This page is the definitive collection of common status codes, transaction types, and risk data structures shared throughout the Trustly platform, including all back-end API responses and client-side SDK interactions.
Consult this documentation for the precise definition of statuses required for handling asynchronous API responses, troubleshooting transaction failures, and interpreting financial verification data.
These codes reflect the current state or reason for failure of a transaction.
These status codes relate to errors found during validation before the transaction is sent to the ODFI, covering risk and validation issues.
| Status Code | Consumer Decline Code | Description | Consumer Messaging | Suggested Actions |
|---|
| SW010 | N/A | Established | N/A | N/A |
| SW013 | User Cancelled | Canceled. | This transaction was cancelled partway by you, your browser or your device. | Prompt user to try again (do not close the browser or app during the transaction). |
| SW020 | N/A | Authorization received | N/A | N/A |
| SW021 | Insufficient Funds | Authorization denied (for example, insufficient funds). | Transaction unsuccessful. We are unable to complete your transaction due to insufficient funds in your account. | See Payment Decline Codes for details and extended reasons. |
| SW051 | Merchant Error | Merchant error (for example, integration issue, invalid request). | Transaction unsuccessful. The transaction could not be completed because of a technical error on the merchant's side. | N/A |
| SW052 | Bank Error | Financial institution error. | Transaction unsuccessful: We're sorry. The transaction could not be completed because of a technical error on the bank's side. | N/A |
| SW053 | Network Error | Internal network error. | Transaction unsuccessful: We're sorry. The transaction could not be completed because of a technical error from the network. | N/A |
| SW054 | Security Controls | Suspicious transaction activity. | Security Alert: We detected some unusual activity and as a result, this transaction was not completed. | Please try again later or use a different bank account. See Payment Decline Codes for details. |
| SW055 | Security Controls | Negative data. | Security Alert: We detected some unusual activity and as a result, this transaction was blocked. | Please contact Trustly's merchant support team if the user escalates. See Payment Decline Codes for details. |
| SW056 | Unsupported Account Type | Invalid account. | Invalid Account: To comply with Federal, state, or local regulations, Trustly does not currently support this type of account. | Please prompt the user to use a personal debitable account. See Payment Decline Codes for details. |
| SW057 | Expired Split Token | Expired split token. | Transaction unsuccessful: We're sorry. The transaction could not be completed because of a technical error on the bank's side. | Please prompt the user to log in again. See Payment Decline Codes for details. |
| SW059 | Security Controls | Instant transaction rejected due to risk. | Security Alert: We detected some unusual activity and as a result, this transaction was not completed. | N/A |
| SW060 | Bank Error | Bank or network processor is down. | Transaction unsuccessful: We're sorry. The transaction could not be completed because of a technical error on the bank's side. | N/A |
These statuses are set when the user cancels the transaction process.
| 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 |
These are the main statuses for ACH and RTP transactions, generally set when user communication is completed or the merchant calls the API directly.
| 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 |
These statuses indicate internal errors related to system functionality.
| Status Code | Description |
|---|
| SE01 | System in maintenance mode |
| SE02 | System error connecting to API services |
| SE03 | System error connecting to financial services gateway |
| Code Set | Range | Description |
|---|
| ACH Return Codes (R) | R01 to R84 | Standard ACH return codes 01 to 84. |
| EFT Decline Codes (Canada) | 900 to 996 | Specific decline codes used for Canadian EFT transactions. |
| TDD Statuses (UK) | ARUCS, ARUDD, AUDDIS | Trustly direct debit specific return codes for the United Kingdom. |
| 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 or Account Mismatch |
| 910 | Payor or Payee Deceased |
| 911 | Account Frozen |
| 912 | Invalid or Incorrect Account No |
| 914 | Incorrect Payor or Payee Name |
| 915 | No Agreement Existed - Business or Personal Refused |
| 916 | Not in accordance with Agreement - Personal |
| 917 | Agreement Revoked - Personal |
| 918 | No Confirmation or 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 |
| 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 |
These codes indicate system-level failures, invalid requests, and security issues encountered during an API call.
Trustly uses conventional HTTP response codes to indicate success or failure of an API request.
| HTTP Status Code | Description |
|---|
| 400 Bad Request | Often due to a missing, required parameter. |
| 401 Unauthorized | Invalid accessId or accessKey. |
| 404 Not Found | This endpoint is not supported or defined by Trustly. |
| 500 Server error | Internal Trustly error. |
| 503 Service Unavailable | The server is currently unable to handle the request due to temporary overloading or server maintenance. |
These codes are returned within the API error response object, providing detail on the failure reason.
| Error Code | Description |
|---|
| 100 | Internal error. An internal database exception occurred when trying to process the request. |
| 150 | Remote error. A remote error (for example, the consumer's bank interface is down) occurred when trying to process the request. |
| 200 | Invalid parameter error. One of the request parameters is invalid (for example, sending an invalid amount format string). |
| 210 | This is a duplicate request. It has been ignored (idempotency failure). |
| 300 | Security error. A generic security error occurred when trying to process the request. |
| 326 | Expired split token |
| 330 | Invalid account |
| 331 | Not enough balance |
| 375 | Access control error. Occurs when a security parameter (accessId, accessKey or requestSignature) is invalid. |
| 380 | Invalid Split Token |
| 390 | Fraud analysis. Suspicious transaction or negative data. |
| 397 | splitToken is not valid |
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. Additionally, in some cases one or more extended reason code may be provided.
| Category | Status Code | Response Description |
|---|
| Decline | SW021 | Authorization denied |
Extended reasons for authorization denied.
| Reason Code | Extended Reason Code | Extended Reason Description | Consumer Decline Reason Details |
|---|
| 12 | 120000 | 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. |
| Category | Status Code | Response Description |
|---|
| Decline | SW054 | Suspicious transaction activity |
Extended reasons for suspicious activity declines.
| Reason Code | Reason Description | Extended Reason Code | Extended Reason Description | Consumer Decline Reason Details |
|---|
| 1 | Exceeded thresholds | 10000 | Exceeded thresholds | 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 FAQs for further information on Trustly's risk decisioning process. |
| 1 | Exceeded thresholds | 10001 | Exceeded transaction amount | 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 FAQs for further information on Trustly's risk decisioning process. |
| 1 | Exceeded thresholds | 11XXX | Exceeded XXX hours consumer amount velocity limit (001 to 999) | 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 FAQs for further information on Trustly's risk decisioning process. |
| 1 | Exceeded thresholds | 12XXX | Exceeded XXX hours consumer count velocity limit (001 to 999) | 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 FAQs for further information on Trustly's risk decisioning process. |
| 1 | Exceeded thresholds | 13XXX | Exceeded XXX hours merchant amount velocity limit (001 to 999) | 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 FAQs for further information on Trustly's risk decisioning process. |
| 1 | Exceeded thresholds | 14XXX | Exceeded XXX days merchant count velocity limit (001 to 999) | 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 FAQs for further information on Trustly's risk decisioning process. |
| 2 | Data mismatch | 20000 | Consumer name data mismatch | 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 FAQs for further information on Trustly's risk decisioning process. |
| 2 | Data mismatch | 20001 | Consumer email data mismatch | 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 FAQs for further information on Trustly's risk decisioning process. |
| 2 | Data mismatch | 20002 | Consumer address data mismatch | 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 FAQs for further information on Trustly's risk decisioning process. |
| 3 | Suspicious History | 30000 | Suspicious History | 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 FAQs for further information on Trustly's risk decisioning process. |
| 3 | Suspicious History | 30101 | NSF ML risk model: Score higher than threshold | 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 FAQs for further information on Trustly's risk decisioning process. |
| 3 | Suspicious History | 30201 | NSF risk rules: Hard block based on attributes | 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 FAQs for further information on Trustly's risk decisioning process. |
| 3 | Suspicious History | 30301 | Fraud ML risk model: Score higher than threshold | 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 FAQs for further information on Trustly's risk decisioning process. |
| 3 | Suspicious History | 30401 | Fraud risk rules: Hard block based on attributes | 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 FAQs for further information on Trustly's risk decisioning process. |
| 4 | 3rd Party Suspicious History | 40000 | 3rd Party Suspicious History | 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 FAQs for further information on Trustly's risk decisioning process. |
| Category | Status Code | Response Description |
|---|
| Decline | SW055 | Negative Data |
| Reason Code | Extended Reason Code | Extended Reason Description | Consumer Decline Reason Details |
|---|
| 5 | 50000 | Negative Database | 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 FAQs for further information on Trustly's risk decisioning process. |
| 5 | 50001 | Consumer blocklisted | 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 FAQs for further information on Trustly's risk decisioning process. |
| 5 | 50002 | Consumer's device blocklisted | 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 FAQs for further information on Trustly's risk decisioning process. |
| 5 | 50003 | Consumer's bank account blocklisted | 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 FAQs for further information on Trustly's risk decisioning process. |
| 5 | 50004 | Consumer's IP blocklisted | 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 FAQs for further information on Trustly's risk decisioning process. |
| 5 | 50005 | Consumer's geo location blocklisted | 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 FAQs for further information on Trustly's risk decisioning process. |
| 5 | 50006 | Uncollected debt: NSF | Transaction unsuccessful. We are unable to complete your transaction because one or more of the consumer's previous transaction(s) were not successful and funds are owed to Trustly. Please request the consumer to contact Trustly to pay for previous transactions to continue. |
| 5 | 50007 | Uncollected debt: Admin | Transaction unsuccessful. We are unable to complete your transaction because one or more of the consumer's previous transaction(s) were not successful as there was an error with bank. Please request the consumer to 1) contact Trustly to pay for previous transactions to continue, 2) login to the bank account again. |
| 5 | 50008 | Uncollected debt: SUF | Transaction unsuccessful. We are unable to complete your transaction because one or more of the consumer's previous transaction(s) were not successful and funds are owed to Trustly. Please request the consumer to contact Trustly to pay for previous transactions to continue. |
| 6 | 60000 | Consumer's on sanctions list | 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 FAQs for further information on Trustly's risk decisioning process. |
| 7 | 70000 | Consumer's on IP sanctions list | 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 FAQs for further information on Trustly's risk decisioning process. |
| 8 | 80000 | Consumer blocklisted by 3rd Party | 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 FAQs for further information on Trustly's risk decisioning process. |
| 16 | 160000 | Unable to communicate reason | Transaction unsuccessful: We're sorry. The transaction could not be completed and no further data is available. |
| Category | Status Code | Response Description |
|---|
| Decline | SW056 | Invalid Account |
| Reason Code | Extended Reason Code | Extended Reason Description | Consumer Decline Reason Details |
|---|
| 9 | 90000 | Unsupported business bank account | Invalid Account: To comply with Federal, state, or local regulations, Trustly does not currently support this type of account. |
| 10 | 100000 | Unsupported non-checking bank account | Invalid Account: To comply with Federal, state, or local regulations, Trustly does not currently support this type of account. |
| Category | Status Code | Response Description |
|---|
| Decline | SW057 | Expired Split Token |
| Reason Code | Extended Reason Code | Extended Reason Description | Consumer Decline Reason Details |
|---|
| 11 | 110000 | Expired/Revoked Split Token | Transaction unsuccessful: We're sorry. The transaction could not be completed because of a technical error on the bank's side. |
| 11 | 110001 | New authentication required due to suspicious activity | Transaction unsuccessful: We're sorry. The transaction could not be completed because of a technical error on the bank's side. |
| Response Code | Reason Code | Suggested Actions |
|---|
| SW054 | 1 | Please try again later or use a different bank account. |
| SW054 | 2 | Please ensure the user is using their own financial institution that matches with the merchant info. |
| SW054 | 3 | Refer to consumer messaging. |
| SW054 | 4 | Refer to consumer messaging. |
| SW054 | 15 | Please ensure that the beneficiary country is not listed among the prohibited countries for international money transfers. |
| SW055 | 5 | Please contact Trustly's merchant support team if the user escalates. |
| SW055 | 6 | Refer to consumer messaging. |
| SW055 | 7 | Please ensure the user is coming from a non-sanctioned country. |
| SW055 | 8 | Please contact Trustly's merchant support team if the user escalates. |
| SW056 | 9 | Please prompt the user to use a personal debitable account. |
| SW056 | 10 | Prompt the user to use a personal debitable account. |
| SW057 | 11 | Please prompt the user to log in again. |
| Value | Name | Description |
|---|
| 0 | New | Initial status after the transaction is created but before the consumer chooses a financial institution for payment. |
| 1 | Pending | Consumer has the Pay Panel open but has not yet authorized the transaction. |
| 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 authorization. |
| 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 (must be done prior to 'Processed' status). |
| 14 | OnHold | A transaction is put on hold after authorization for merchant approval/investigation. |
These codes define the type of bank connectivity or payment instrument used.
| Code | Description |
|---|
| 1 | Online Banking (Direct connection) |
| 2 | Manual Electronic Check |
| Value | Name | Description |
|---|
| 2 | Deferred | Payment is authorized, but requires a separate Capture API call to debit funds. Multiple captures $\le$ original amount are possible. |
| 3 | Recurring | Same as deferred, but associated with a payment agreement (defines amount/timing of capture). |
| 4 | Disbursement | Payment type used exclusively for mass disbursements. |
| 5 | Verification | Used solely to verify the customer account outside of the Trustly system. |
| 6 | Retrieval | Data retrieval to fetch account and user information without a payment request. |
| Value | Name | Description |
|---|
| 0 | External | Transaction created when the Feedback API updates the status of a Retrieval paymentType. |
| 1 | Authorize | Transaction created with paymentType is Deferred or Recurring. |
| 2 | Pay | Transaction created with paymentType of Instant. |
| 3 | Capture | Capture transactions are created with the Capture API. |
| 4 | Refund | Refund 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 | An attempt to reprocess a previously denied Capture transaction. |
| 9 | Tokenization | |
| 10 | Preauthorization | Preauthorization transactions are created with the Preauthorization API. |
| 11 | Guarantee | |
| Code | Name | Description |
|---|
| 1 | VerifiedByMerchant | ... |
| 2 | ApprovedByMerchant | ... |
| 3 | VerifiedByTrustly | ... |
| 4 | AmountAuthorizedByMerchant | ... |
| Code | Name | Description |
|---|
| 1 | Automatic | Payment verification followed Trustly internal rules. |
| 2 | ToVerify | Transaction is held (status = OnHold) pending merchant approval/investigation. |
| 3 | Verified | Payment was verified and approved by the merchant or Trustly. |
| 4 | Refused | Payment was denied after verification. |
| 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. |
These values identify the type of bank account being used.
| Code | Description |
|---|
| -1 | Unknown |
| 0 | Other |
| 1 | Checking |
| 2 | Savings |
These values define the ownership profile of the bank account.
| Code | Description |
|---|
| -1 | Unknown |
| 0 | Other |
| 1 | Personal |
| 2 | Business |
