Type Definitions
This is a collection of common type definitions that are shared between objects.
Payment Provider Transaction Status Codes
Software (SW)
These statuses are related errors found during the validation processes before the transaction is sent to the ODFI. These include risk and validation errors.
Status Code | Description |
---|---|
SW010 | Established |
SW013 | Canceled |
SW020 | Authorization received |
SW021 | Authorization declined due to insufficient funds |
SW051 | Merchant error |
SW052 | Financial Institution error |
SW053 | Internal network error |
SW054 | Suspicious transaction activity |
SW055 | Negative data |
SW056 | Invalid account |
SW057 | Expired split token |
SW059 | Instant transaction rejected due to risk |
SW060 | Bank or network processor is down |
User Canceled
These statuses are related to when the user cancels the transaction process. Each time the user cancels a status based on the point of cancellation is defined. Therefore, errors during user interaction.
Status Code | Description |
---|---|
UC01 | User canceled the transaction at bank selection page |
UC02 | User canceled the transaction at login page |
UC03 | User canceled the transaction at invalid login page |
UC04 | User canceled the transaction at challenge question page |
UC05 | User canceled the transaction at invalid answers for challenge questions page. |
UC06 | User canceled the transaction at MFA page |
UC07 | User canceled the transaction at invalid MFA page |
UC08 | User canceled the transaction at account selection page |
UC09 | User canceled the transaction at error page |
UC10 | User canceled the transaction at partial account number page |
UC11 | User canceled the transaction at select account location page |
UC12 | User canceled the transaction because it does not have a bank on the list |
UC13 | User canceled the transaction at login with captcha page |
UC14 | User canceled the transaction at captcha validation page |
UC15 | User canceled the transaction at manual account input page |
UC16 | User canceled the transaction at manual account confirmation page |
UC17 | User canceled the transaction at MCD confirmation page |
UC18 | User canceled the transaction at MCD validation page |
UC19 | User canceled the transaction at account profile input page |
UC20 | User canceled the transaction at no dynamic balance page |
UC21 | User canceled the transaction at partial account not supported page |
UC22 | User canceled the transaction at security script page |
UC23 | User canceled the transaction at account not supported page |
UC24 | User canceled the transaction at authorize page with exception |
UC25 | User canceled the transaction at bad account page |
UC26 | User canceled the transaction at the bank's reset password screen |
UC27 | User canceled the transaction because the bank was unavailable |
UC28 | User canceled the transaction at an external screen |
UC29 | User canceled the transaction due to a timeout |
UC30 | User canceled on the manual entry screen after an invalid routing or account number entry |
UC31 | User canceled on the manual entry screen due to related information (SWIFT code or address) not being found |
UC32 | User canceled the transaction at the maintenance page |
UC33 | User canceled the transaction at non-eligible currency error page |
UC34 | User canceled the transaction at Connect to your bank (OAuth login) page |
UC35 | User canceled the transaction at Waiting for your approval page |
UC36 | User canceled the transaction at VAN info page |
UC37 | User canceled the transaction at widget within Lightbox page |
UC39 | User canceled the transaction indirectly by allowing the FI OAuth login session to expire |
Acknowledged Communication (AC)
These are the main statuses for ACH and RTP transactions. When user communication is completed or when the merchant calls API directly these are going to be set for the transaction.
Status Code | Description |
---|---|
AC100 | AC Pending |
AC101 | AC Declined |
AC102 | AC Approved |
AC103 | AC Error |
AC104 | AC Voided |
AC105 | AC Processed |
AC106 | AC Collected |
AC107 | AC Awaiting Capture |
AC108 | AC Awaiting Approval |
AC109 | AC Suspended |
AC110 | AC In Collection |
AC111 | AC In Research |
AC112 | AC Disputed |
AC113 | AC Uncollected, Insufficient Funds |
AC114 | AC Invalid or Closed Account |
AC115 | AC Other Returns |
AC116 | AC None |
AC117 | AC Expired |
AC118 | AC Settled |
System Error (SE)
Status Code | Description |
---|---|
SE01 | System in maintenance mode |
SE02 | System error connecting to API services |
SE03 | System error connecting to financial services gateway |
ACH Return Codes (R)
These statuses are related to ACH return codes.
Status Code | Description |
---|---|
R01 to R84 | ACH return codes 01 to 84. |
EFT Decline Codes - Canada
These statuses are related to ACH return codes.
Status Code | Description |
---|---|
900 | Account information incorrectly entered |
901 | Insufficient Funds |
902 | Account not Found |
903 | Payment Stopped/Recalled |
904 | Post/Stale Dated |
905 | Account Closed |
907 | No Debit Allowed |
908 | Funds Not Cleared |
909 | Currency/Account Mismatch |
910 | Payor/Payee Deceased |
911 | Account Frozen |
912 | Invalid/Incorrect Account No |
914 | Incorrect Payor/Payee Name |
915 | No Agreement Existed - Business/Personal Refused |
916 | Not in accordance with Agreement - Personal |
917 | Agreement Revoked - Personal |
918 | No Confirmation/Pre-Notification - Personal |
919 | Not in accordance with Agreement - Business |
920 | Agreement Revoked - Business |
921 | No Pre-Notification - Business |
922 | Customer Initiated Return - Credit Only |
990 | Institution in Default |
996 | Chargeback |
Trustly Direct Debit (TDD) for UK
These statuses are related to ACH return codes.
Status Code | Description |
---|---|
ARUCS_0 | Invalid details |
ARUCS_2 | Beneficiary deceased |
ARUCS_3 | Account transferred |
ARUCS_5 | No account |
ARUCS_B | Account closed |
ARUCS_C | Requested by remitter |
AWACS_0 | Invalid details |
AWACS_3 | Account transferred |
ARUDD_0 | Refer to payer (basically means out of funds) |
ARUDD_2 | Payer deceased |
ARUDD_3 | Account transferred |
ARUDD_4 | Advance notice disputed |
ARUDD_5 | No account (or wrong account type) |
ARUDD_6 | No instruction |
ARUDD_7 | Amount differs (disputed amount) |
ARUDD_8 | Amount not yet due (in case payment is sent before DDI confirmed) |
ARUDD_9 | Presentation is overdue |
ARUDD_A | Service User differs (Details dont match DDI) |
ARUDD_B | Account closed |
ADDACS_0 | Instruction canceled refer to Payer |
ADDACS_1 | Instruction canceled by Payer |
ADDACS_2 | Payer Deceased |
ADDACS_3 | Account transferred to new bank |
ADDACS_B | Account closed |
ADDACS_C | Account transferred to new branch |
ADDACS_D | Advance notice disputed |
ADDACS_E | Instruction amended |
ADDACS_R | Instruction re-instated |
AUDDIS_1 | Instruction Canceled by Payer |
AUDDIS_2 | Payer deceased |
AUDDIS_3 | Account transferred |
AUDDIS_5 | No Account |
AUDDIS_6 | No instruction |
AUDDIS_C | DDI amount not zero |
AUDDIS_F | Invalid account type |
AUDDIS_G | PSP will not accept DD on account |
AUDDIS_H | Instruction expired |
AUDDIS_I | Payer Reference not unique |
AUDDIS_K | Instruction cancelled by paying PSP |
AUDDIS_L | Incorrect payers account details |
AUDDIS_M | Trx code/user status incompatible |
AUDDIS_N | Trx not allowed at payers branch |
AUDDIS_O | invalid reference |
AUDDIS_P | Payer's name not present |
AUDDIS_Q | Service users name blank |
DDICA_1 | Amount differs |
DDICA_2 | No advance notice received by payer |
DDICA_3 | DDI canceled by bank |
DDICA_4 | Payer has canceled DDI with Service User |
DDICA_5 | No instruction held |
DDICA_6 | Signature fraudulent |
DDICA_7 | Claim raised at Service User Request |
DDICA_8 | Service user name disputed, payer does not recognize |
Payment Response Codes
Category | Response Code | Response Description | Suggested Actions |
---|---|---|---|
Status - New transaction | SW010 | Established | N/A |
Status - User canceled | SW013 | Canceled (user canceled the transaction) | Prompt user to try again (do not close the browser or app during the transaction.) For suggested copy see consumer messaging below. |
Status - Transaction authorized | SW020 | Authorization received | N/A |
Payment Decline Codes
When a payment transaction is declined it will terminate with a "Failed" status and a decline code may be assigned to the transaction. Additionally, if your application is configured for Event notifications a Fail
event will be sent to your application's notificationUrl
.
Category | Response Code | Response Description | Suggested Actions |
---|---|---|---|
Decline | SW021 | Authorization denied | The account selected does not have sufficient funds. Please prompt the user to use another bank account or lower the transaction amount. For suggested copy see consumer messaging below. |
Decline | SW051 | Merchant error | Integration error - please contact Trustly's integration team. Popular reasons are: sent invalid request or mandatory fields in the request are missing. For suggested copy see consumer messaging below. |
Decline | SW052 | Financial institution error | User's online financial institution error (ex. financial institution is under maintenance, financial institution website is down). For suggested copy see consumer messaging below. |
Decline | SW053 | Internal network error | Generic error For suggested copy see consumer messaging below. |
Decline | SW059 | Instant transaction rejected due to risk | Instant payout transaction rejection due to consumer's risk profile. For suggested copy see consumer messaging below. |
Decline | SW060 | Bank or network processor is down | Instant payout bank is down or instant payout network (TCH) is down |
Some decline codes will be accompanied by a ReasonCode
and ReasonDescription
these fields can be used to inform your users the reason for decline and if some alternative actions are suggested.
Category | Response Code | Response Description | Reason Code | Reason Description | Suggested Actions |
---|---|---|---|---|---|
Decline | SW054 | Suspicious transaction activity | 1 | Exceeded thresholds | Please try again later or use a different bank account. For suggested copy see consumer messaging below. |
Decline | SW054 | Suspicious transaction activity | 2 | Data mismatch | Please ensure the user is using their own financial institution that matches with the merchant info. For suggested copy see consumer messaging below. |
Decline | SW054 | Suspicious transaction activity | 3 | Suspicious History | For suggested copy see consumer messaging below. |
Decline | SW054 | Suspicious transaction activity | 4 | 3rd Party Suspicious History | For suggested copy see consumer messaging below. |
Decline | SW054 | Suspicious transaction activity | 15 | Country Block | Please ensure that the beneficiary country is not listed among the prohibited countries for international money transfers. For suggested copy see consumer messaging below. |
Decline | SW055 | Negative data | 5 | Negative Database | Please contact Trustly's merchant support team if the user escalates. For suggested copy see consumer messaging below. |
Decline | SW055 | Negative data | 6 | Sanctions | For suggested copy see consumer messaging below. |
Decline | SW055 | Negative data | 7 | IP Sanctions | Please ensure the user is coming from a non-sanctioned country. For suggested copy see consumer messaging below. |
Decline | SW055 | Negative data | 8 | Negative Database | Please contact Trustly's merchant support team if the user escalates. For suggested copy see consumer messaging below. |
Decline | SW056 | Invalid account | 9 | Business Account Unsupported (Regulatory Reasons) | Please prompt the user to use a personal debitable account. For suggested copy see consumer messaging below. |
Decline | SW056 | Invalid account | 10 | AccountUnsupported (Regulatory Reasons) | Please prompt the user to use a personal debitable account. For suggested copy see consumer messaging below. |
Decline | SW057 | Expired Split Token | 11 | Expired Split Token | Please prompt the user to log in again. For suggested copy see consumer messaging below. |
Payment Response Consumer Messaging
Use the following consumer codes and language in applicable user experiences and messaging.
Response Code | Consumer Decline Code | Consumer Decline Reason Details |
---|---|---|
SW013 | User Cancelled | This transaction was cancelled partway by you, your browser or your device. |
SW021 | Insufficient Funds | Transaction unsuccessful. We are unable to complete your transaction due to insufficient funds in your account. Please a) add funds to your account, b) Use another account at the same bank, c) Or, sign in to another bank |
SW051 | Merchant Error | Transaction unsuccessful: We're sorry. The transaction could not be completed because of a technical error on the merchant's side. |
SW052 | Bank Error | Transaction unsuccessful: We're sorry. The transaction could not be completed because of a technical error on the bank's side. |
SW053 | Network Error | Transaction unsuccessful: We're sorry. The transaction could not be completed because of a technical error from the network. |
SW054 | Security Controls | Security Alert: We detected some unusual activity and as a result, this transaction was not completed. To protect consumers and merchants, Trustly employs risk mitigation and fraud prevention tools to spot suspicious activity. Please see Trustly's help center for further information on Trustly's risk decisioning process. |
SW055 | Security Controls | Security Alert: We detected some unusual activity and as a result, this transaction was blocked. To protect consumers and merchants, Trustly employs risk mitigation and fraud prevention tools to spot suspicious activity. Please see Trustly's help center for further information on Trustly's risk decisioning process. |
SW056 | Unsupported Account Type | Invalid Account: To comply with Federal, state, or local regulations, Trustly does not currently support this type of account. |
SW059 | Security Controls | Security Alert: We detected some unusual activity and as a result, this transaction was not completed. To protect consumers and merchants, Trustly employs risk mitigation and fraud prevention tools to spot suspicious activity. Please see Trustly's help center for further information on Trustly's risk decisioning process. |
SW060 | Bank Error | Transaction unsuccesful: We're sorry. The transaction could not be completed because of a technical error on the bank's side. |
Payment Provider Types
Code | Description |
---|---|
1 | Online Banking |
2 | Manual Electronic Check |
Payment Types
Value | Name | Description |
---|---|---|
2 | Deferred | Deferred payment. Payment is authorized but the capture operation must be called to initiate the debit. You can start to initiate multiple captures that are less than or equal to the original transaction authorization amount. |
3 | Recurring | Recurring payment. Same as deferred but associated with a payment agreement between consumer and merchant that defines how much and when the capture can be started. |
4 | Disbursement | Disbursement payment. This payment type can only be used for disbursements. |
5 | Verification | This payment type is used to verify the customer financial institution account as the payments will be done outside of Trustly system. |
6 | Retrieval | Data retrieval. This payment type is used to retrieve account and user information from Trustly without an associated payment request. This payment type is not enabled by default. Contact Trustly if you need this feature. |
Transaction Status Values
Value | Name | Description |
---|---|---|
0 | New | This is the initial status after the transaction is created but before the consumer chooses a financial institution for payment. Transactions in the new state are visible only through Notification or the API status operations, not through the Merchant Portal. |
1 | Pending | Payment is pending. This is the initial transaction status when the consumer has the Pay Panel open but has not yet authorized the transaction. Transactions in the Pending state are visible only through Notification or the API status operations, not through the Merchant Portal. |
2 | Authorized | Payment was authorized by the consumer (they have selected their account and clicked ‘Pay') but the ACH has not yet been submitted for processing. |
3 | Processed | Transaction was processed. The ACH debit has been submitted to the ACH network after authorization by the consumer. |
4 | Completed | Transaction was paid, funds transferred. |
5 | Failed | Internal failure of transaction. (Unrelated to the merchant). |
6 | Expired | Pending transaction timed out before the consumer authorized the payment via the Pay Panel. |
7 | Canceled | Transaction was canceled by the consumer by closing the Pay Panel prior to the transaction being authorized or canceling the transaction from the Pay Panel. |
8 | Denied | Money transfer was denied, consumer account does not have enough funds. |
10 | Reversed | Payment was reversed (charged back by the bank or Trustly). |
11 | Partially Refunded | Payment was partially refunded. |
12 | Refunded | Payment was refunded. |
13 | Voided | Authorization was voided by the merchant. This occurs when the 'cancel' API is invoked or the transaction is canceled in the Merchant Portal (this must be done prior to the transaction being moved to ‘Processed' status). |
14 | OnHold | A transaction is put on hold after authorization if something is preventing the normal flow, such as when an ACH debit could not be initiated, or if the Trustly wants the merchant to verify that it really approves of this customer authorizing this amount. The payment may take longer to process than usual. Note: if a transaction is On Hold, you can verify it through the Merchant Portal to let it resume the normal flow of payment processing. Currently, there is no equivalent way to do that verification through the API. |
Transaction Types
Value | Name | Description |
---|---|---|
0 | External | This transaction is created when the Feedback API is called to update the status of a transaction created with a paymentType of Retrieval . |
1 | Authorize | This is a transaction created with paymentType is Deferred or Recurring . |
2 | Pay | This is a transaction created with paymentType of Instant . |
3 | Capture | Capture transactions are created with the Capture API. |
4 | Refund | Capture transactions are created with the Refund API. |
5 | Reverse | A reverse transaction is created when the payment is charged back by the bank (payment provider). |
6 | Deposit | Deposit transactions are created with the Deposit API. |
7 | Reclaim | Reclaim transactions are created with the Reclaim API. |
8 | Representment | A representment transaction represents an attempt to reprocess a previously denied Capture transaction. |
9 | Tokenization | |
10 | Preauthorization | Preauthorization transactions are created with the Preauthorization API. |
11 | Guarantee |
Verification Mode
Code | Name | Description |
---|---|---|
1 | VerifiedByMerchant | ... |
2 | ApprovedByMerchant | ... |
3 | VerifiedByTrustly | ... |
4 | AmountAuthorizedByMerchant | ... |
Verification Status
Code | Name | Description |
---|---|---|
1 | Automatic | Payment verification followed Trustly internal rules. |
2 | ToVerify | Payment transaction is held (status = OnHold ) for further investigation and approval by the merchant. |
3 | Verified | Payment was verified and approved by the merchant or Trustly (see Verification Mode). |
4 | Refused | Payment was denied by the merchant or Trustly after verification. |
Verification Types
Code | Name | Description |
---|---|---|
0 | Not Verified | The Account was not verified. |
1 | Micro-deposits | The Account was verified using a micro-deposit process. |
2 | Online Banking verification | The Account was verified using the Trustly Online Banking application. |
3 | Database verification | The Account was verified using the Trustly database or a Third Party Service. |
FCRA Verification Third Party Score Values
The table below maps Trustly Verification thirdParty
values to a related score
value.
Score | Description | Verified Mapping |
---|---|---|
0 | Failed RT validation. | 0 |
100 | Strong indication that this account is invalid for payments. | 1 |
200 | This account has recent non-bankable debts. | 2 |
300 | History of returns on the account. | 3 |
400 | No negative data on this account, but the format appears suspicious. | 4 |
500 | No data on this account or format. | 5 |
600 | Limited information on the account, but the format appears valid. | 6 |
700 | We have seen this account, but did not receive a final disposition on the transaction. | 7 |
800 | We have seen this account but not recently. | 8 |
900 | This account has been seen recently. | 9 |
999 | Highest confidence that this account is valid. | 10 |
Non-FCRA Verification Score Values
The table below maps Trustly non-FCRA Verification score
values to a related verified
value.
Score | Description | Verified Mapping |
---|---|---|
15 | Known bad bank account. | false |
20 | Unknown bank account, but format appears valid. | false |
25 | Unknown bank account, but format appears suspicious. | false |
35 | Bank account seen but transaction not yet settled (5 days). | true |
45 | Known good bank account. | true |
Financial Institution Account Type Values
Code | Description |
---|---|
-1 | Unknown |
0 | Other |
1 | Checking |
2 | Savings |
Financial Institution Account Profile Values
Code | Description |
---|---|
-1 | Unknown |
0 | Other |
1 | Personal |
2 | Business |
Updated 11 days ago