Reference
Which code should I use?
Your operations support team will guide with this based on the use case you are trying to support.
Directions
Direction | Description |
---|---|
Inbound | Payment we received from another bank |
Outbound | Payment we are sending to another bank |
Payment Types
Type | Description |
---|---|
Transfer | A new payment originating from either Cross River or another bank. Most payments are of this type. |
Drawdown | A drawdown request |
DrawdownResponse | A response to a drawdown request |
ServiceMessage | A non-value message sent from one bank to another. For informational purposes only. |
Reversal | A reversal of a previously sent wire payment |
Payment Status
Status | Description |
---|---|
Created | We have received the payment, but have not started processing it yet. This status should only appear briefly under normal circumstances. |
Pending | The payment is waiting to be batched and sent to the Federal Reserve. |
Hold | Payment is being held at the moment and reviewed by our operations team. |
Batched | The payment has been batched is a final review is being done before we send it out in a file to the Federal Reserve. |
Processing | For inbound payments, we are attempting to post the payment to the receiving account. For outbound payments, the payment has been sent to the Federal Reserve, but has not posted yet. An outbound standard payment may remain in this status for a day or more. |
Completed | The payment has been posted and accepted by the Federal Reserve (in the case of outbound payments). This is a final status. |
Canceled | An outbound payment has be canceled at the request of the partner. A payment may only be canceled while either pending or on hold. This is a final status. |
Rejected | Our operations team was unable to process the payment and has rejected it. In the case of inbound, the payment has been returned to the originating bank. This is a final status. |
Business Function Codes
Code | Description |
---|---|
CTR | Customer Transfer |
SVC | Service Message (non-value) |
ID Codes
Code | Description |
---|---|
B | SWIFT Bank Identifier Code (BIC) |
C | CHIPS Participant |
D | Demand Deposit Account (DDA) Number |
F | Fed Routing Number |
T | SWIFT BIC or Bank Entity Identifier (BEI) and account number |
U | CHIPS Identifier |
1 | Passport Number |
2 | Tax Identification Number |
3 | Driverโs License Number |
4 | Alien Registration Number |
5 | Corporate Identification |
9 | Other Identification |
Type Codes
Code | Description |
---|---|
10 | Funds Transfer - A funds transfer in which the sender and/or receiver may be a bank or a third party (i.e., customer of a bank). |
15 | Foreign Transfer - A funds transfer to or from a foreign central bank or government or international organization with an account at the Federal Reserve Bank of New York. |
16 | Settlement Transfer - A funds transfer between Fedwire Funds Service participants. |
Sub Type Codes
Code | Description |
---|---|
00 | Basic Funds Transfer |
01 | Request for Reversal |
02 | Reversal of Transfer |
07 | Request for Reversal of a Prior Day Transfer |
08 | Reversal of a Prior Day Transfer |
31 | Request for Credit (Drawdown) |
32 | Funds Transfer Honoring a Request for Credit (Drawdown) |
33 | Refusal to Honor a Request for Credit (Drawdown) |
90 | Service Message |
Error Codes
Code | Description |
---|---|
1000 | General exception |
1001 | Config required |
2000 | General exception |
2001 | Payment not found |
2002 | Invalid payment status |
2003 | Direction not inbound |
2004 | Direction not outbound |
2005 | Posting account cannot be changed as posting completed |
2006 | Acknowledgment required |
2007 | Originator account not found |
2008 | Origination not enabled for account |
2009 | Custom originator data not allowed for account |
2010 | Origination not allowed from a restricted account |
2011 | Receiver routing number not found |
2012 | Source wire not found |
2013 | Source wire message unavailable |
2014 | Service messages cannot be reversed |
2015 | Payment type cannot be reversed |
2016 | Payment must be completed before it can be reversed |
2017 | Only inbound payments can be reversed |
2018 | Invalid source business function code |
2019 | Payment must be completed before it can be responded to |
2020 | Only inbound payments can be responded to |
2021 | Original wire not found |
2022 | Beneficiary account not found |
2023 | Account not found |
2024 | Posting already completed |
2025 | Posting must be failed to attempt a retry |
2200 | Invalid submission status |
2201 | Submission must be pending |
2202 | Submission must be processing |
2203 | Submission must be created |
2300 | Distribution must be pending |
2301 | Distribution must be verified |
2302 | Distribution must be released |
2303 | Distribution must be generating |
2304 | Distribution must not be released |
2305 | Distribution already canceled |
2306 | No payments to distribute |
2307 | Distribution currently generating |
2308 | Distribution must be transmitted |
2309 | Distribution must be transmitted but not acknowledged |
2400 | Hold is not active |
2401 | Hold is not evaluating |
2500 | Scan already pending |
2501 | No scan lists are configured for account |
2502 | Payment type must be a transfer |
2503 | Payment must be on hold to request a rescan |
2550 | Invalid posting record status |
2600 | This action requires dual control |
2601 | Accounts must be unique |
2602 | Inbound Suspense Account not found |
2603 | Outbound Suspense Account not found |
2604 | Operator Account not found |
2605 | Unposted Account not found |
2606 | Change not approved |
2607 | Change not approved |
2608 | Global profile not found or is invalid |
3000 | General exception |
3001 | Origination payment amount exceeds user permissions |
3002 | Clearing hold exceeds user permissions for payment amount |
3003 | Clearing hold exceeds user permissions for payment amount |
3004 | User not authorized to reject inbound wires |
3005 | Distribution max wire amount exceeds user permissions |
Updated over 1 year ago