Transaction Status
Transaction Lifecycle
Different types of transactions go through different statuses. The lifecycles for capture/deposit and Refund/reclaim transactions are outlined below.
Capture and Deposit Transactions
Refund and Reclaim Transactions
Transaction Status Values
A transaction can go through the following statuses:
Status | Description |
---|---|
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. |
Pending | Payment is pending. This is the initial transaction status when the consumer has the Payment Lightbox 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. |
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. |
Processed | Transaction was processed. The ACH debit has been submitted to the ACH network after authorization by the consumer. |
Completed | Transaction was paid, funds transferred. |
Failed | Internal failure of transaction. (Unrelated to the merchant). |
Expired | Pending transaction timed out before the consumer authorized the payment via the Payment Lightbox. |
Canceled | Transaction was canceled by the consumer by closing the Payment Lightbox prior to the transaction being authorized or canceling the transaction from the Payment Lightbox. |
Denied | Money transfer was denied, transaction was returned from consumer account |
Reversed | Payment was reversed (charged back by the bank or Trustly). |
Partially Refunded | Payment was partially refunded. |
Refunded | Payment was refunded. |
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). |
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. |
Status Codes
Each transaction status also has a transaction code that provides more detail, they are as follows:
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 |
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 |
Updated 5 months ago