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 CodeDescription
SW010Established
SW013Canceled
SW020Authorization received
SW021Authorization declined due to insufficient funds
SW051Merchant error
SW052Financial Institution error
SW053Internal network error
SW054Suspicious transaction activity
SW055Negative data
SW056Invalid account
SW057Expired split token
SW059Instant transaction rejected due to risk
SW060Bank 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 CodeDescription
UC01User canceled the transaction at bank selection page
UC02User canceled the transaction at login page
UC03User canceled the transaction at invalid login page
UC04User canceled the transaction at challenge question page
UC05User canceled the transaction at invalid answers for challenge questions page.
UC06User canceled the transaction at MFA page
UC07User canceled the transaction at invalid MFA page
UC08User canceled the transaction at account selection page
UC09User canceled the transaction at error page
UC10User canceled the transaction at partial account number page
UC11User canceled the transaction at select account location page
UC12User canceled the transaction because it does not have a bank on the list
UC13User canceled the transaction at login with captcha page
UC14User canceled the transaction at captcha validation page
UC15User canceled the transaction at manual account input page
UC16User canceled the transaction at manual account confirmation page
UC17User canceled the transaction at MCD confirmation page
UC18User canceled the transaction at MCD validation page
UC19User canceled the transaction at account profile input page
UC20User canceled the transaction at no dynamic balance page
UC21User canceled the transaction at partial account not supported page
UC22User canceled the transaction at security script page
UC23User canceled the transaction at account not supported page
UC24User canceled the transaction at authorize page with exception
UC25User canceled the transaction at bad account page
UC26User canceled the transaction at the bank's reset password screen
UC27User canceled the transaction because the bank was unavailable
UC28User canceled the transaction at an external screen
UC29User canceled the transaction due to a timeout
UC30User canceled on the manual entry screen after an invalid routing or account number entry
UC31User canceled on the manual entry screen due to related information (SWIFT code or address) not being found
UC32User canceled the transaction at the maintenance page
UC33User canceled the transaction at non-eligible currency error page
UC34User canceled the transaction at Connect to your bank (OAuth login) page
UC35User canceled the transaction at Waiting for your approval page
UC36User canceled the transaction at VAN info page
UC37User 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 CodeDescription
AC100AC Pending
AC101AC Declined
AC102AC Approved
AC103AC Error
AC104AC Voided
AC105AC Processed
AC106AC Collected
AC107AC Awaiting Capture
AC108AC Awaiting Approval
AC109AC Suspended
AC110AC In Collection
AC111AC In Research
AC112AC Disputed
AC113AC Uncollected, Insufficient Funds
AC114AC Invalid or Closed Account
AC115AC Other Returns
AC116AC None
AC117AC Expired
AC118AC Settled

System Error (SE)

Status CodeDescription
SE01System in maintenance mode
SE02System error connecting to API services
SE03System error connecting to financial services gateway

ACH Return Codes (R)

These statuses are related to ACH return codes.

Status CodeDescription
R01 to R84ACH return codes 01 to 84.

EFT Decline Codes - Canada

These statuses are related to ACH return codes.

Status CodeDescription
900Account information incorrectly entered
901Insufficient Funds
902Account not Found
903Payment Stopped/Recalled
904Post/Stale Dated
905Account Closed
907No Debit Allowed
908Funds Not Cleared
909Currency/Account Mismatch
910Payor/Payee Deceased
911Account Frozen
912Invalid/Incorrect Account No
914Incorrect Payor/Payee Name
915No Agreement Existed - Business/Personal Refused
916Not in accordance with Agreement - Personal
917Agreement Revoked - Personal
918No Confirmation/Pre-Notification - Personal
919Not in accordance with Agreement - Business
920Agreement Revoked - Business
921No Pre-Notification - Business
922Customer Initiated Return - Credit Only
990Institution in Default
996Chargeback

Trustly Direct Debit (TDD) for UK

These statuses are related to ACH return codes.

Status CodeDescription
ARUCS_0Invalid details
ARUCS_2Beneficiary deceased
ARUCS_3Account transferred
ARUCS_5No account
ARUCS_BAccount closed
ARUCS_CRequested by remitter
AWACS_0Invalid details
AWACS_3Account transferred
ARUDD_0Refer to payer (basically means out of funds)
ARUDD_2Payer deceased
ARUDD_3Account transferred
ARUDD_4Advance notice disputed
ARUDD_5No account (or wrong account type)
ARUDD_6No instruction
ARUDD_7Amount differs (disputed amount)
ARUDD_8Amount not yet due (in case payment is sent before DDI confirmed)
ARUDD_9Presentation is overdue
ARUDD_AService User differs (Details dont match DDI)
ARUDD_BAccount closed
ADDACS_0Instruction canceled refer to Payer
ADDACS_1Instruction canceled by Payer
ADDACS_2Payer Deceased
ADDACS_3Account transferred to new bank
ADDACS_BAccount closed
ADDACS_CAccount transferred to new branch
ADDACS_DAdvance notice disputed
ADDACS_EInstruction amended
ADDACS_RInstruction re-instated
AUDDIS_1Instruction Canceled by Payer
AUDDIS_2Payer deceased
AUDDIS_3Account transferred
AUDDIS_5No Account
AUDDIS_6No instruction
AUDDIS_CDDI amount not zero
AUDDIS_FInvalid account type
AUDDIS_GPSP will not accept DD on account
AUDDIS_HInstruction expired
AUDDIS_IPayer Reference not unique
AUDDIS_KInstruction cancelled by paying PSP
AUDDIS_LIncorrect payers account details
AUDDIS_MTrx code/user status incompatible
AUDDIS_NTrx not allowed at payers branch
AUDDIS_Oinvalid reference
AUDDIS_PPayer's name not present
AUDDIS_QService users name blank
DDICA_1Amount differs
DDICA_2No advance notice received by payer
DDICA_3DDI canceled by bank
DDICA_4Payer has canceled DDI with Service User
DDICA_5No instruction held
DDICA_6Signature fraudulent
DDICA_7Claim raised at Service User Request
DDICA_8Service user name disputed, payer does not recognize

Payment Response Codes

CategoryResponse CodeResponse DescriptionReason CodeReason DescriptionNext Steps
Status - New txnSW010EstablishedN/A
Status - User canceledSW013Canceled (user canceled the transaction)Prompt user to try again (do not close the browser or app during the transaction.)
Status - txn authorizedSW020Authorization receivedN/A
DeclineSW021Authorization deniedThe account selected does not have sufficient funds. Please prompt the user to use another bank account or lower the transaction amount.
DeclineSW051Merchant errorIntegration error - please contact Trustly's integration team. Popular reasons are: sent invalid request or mandatory fields in the request are missing.
DeclineSW052Financial institution errorUser's online financial institution error (ex. financial institution is under maintenance, financial institution website is down).
DeclineSW053Internal network errorGeneric error
DeclineSW054Suspicious transaction activity1Exceeded thresholdsPlease try again later or use a different bank account
DeclineSW054Suspicious transaction activity2Data mismatchPlease ensure the user is using their own financial institution that matches with the merchant info
DeclineSW054Suspicious transaction activity3Suspicious HistoryN/A
DeclineSW054Suspicious transaction activity43rd Party Suspicious HistoryN/A
DeclineSW055Negative data5Negative DatabasePlease contact Trustly's merchant support team if the user escalates.
DeclineSW055Negative data6Sanctions
DeclineSW055Negative data7IP SanctionsPlease ensure the user is coming from a non-sanctioned country.
DeclineSW055Negative data8Negative DatabasePlease contact Trustly's merchant support team if the user escalates.
DeclineSW056Invalid account9Business Account Unsupported (Regulatory Reasons)Please prompt the user to use a personal debitable account.
DeclineSW056Invalid account10AccountUnsupported (Regulatory Reasons)Please prompt the user to use a personal debitable account.
DeclineSW057Expired Split Token11Expired Split TokenPlease prompt the user to log in again
DeclineSW059Instant transaction rejected due to riskInstant payout transaction rejection due to consumer's risk profile
DeclineSW060Bank or network processor is downInstant payout bank is down or instant payout network (TCH) is down

Payment Provider Types

CodeDescription
1Online Banking
2Manual Electronic Check

Payment Types

ValueNameDescription
2DeferredDeferred 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.
3RecurringRecurring 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.
4DisbursementDisbursement payment. This payment type can only be used for disbursements.
5VerificationThis payment type is used to verify the customer financial institution account as the payments will be done outside of Trustly system.
6RetrievalData 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

ValueNameDescription
0NewThis 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.
1PendingPayment 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.
2AuthorizedPayment was authorized by the consumer (they have selected their account and clicked ‘Pay') but the ACH has not yet been submitted for processing.
3ProcessedTransaction was processed. The ACH debit has been submitted to the ACH network after authorization by the consumer.
4CompletedTransaction was paid, funds transferred.
5FailedInternal failure of transaction. (Unrelated to the merchant).
6ExpiredPending transaction timed out before the consumer authorized the payment via the Pay Panel.
7CanceledTransaction was canceled by the consumer by closing the Pay Panel prior to the transaction being authorized or canceling the transaction from the Pay Panel.
8DeniedMoney transfer was denied, consumer account does not have enough funds.
10ReversedPayment was reversed (charged back by the bank or Trustly).
11Partially RefundedPayment was partially refunded.
12RefundedPayment was refunded.
13VoidedAuthorization 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).
14OnHoldA 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

ValueNameDescription
0ExternalThis transaction is created when the Feedback API is called to update the status of a transaction created with a paymentType of Retrieval.
1AuthorizeThis is a transaction created with paymentType is Deferred or Recurring.
2PayThis is a transaction created with paymentType of Instant.
3CaptureCapture transactions are created with the Capture API.
4RefundCapture transactions are created with the Refund API.
5ReverseA reverse transaction is created when the payment is charged back by the bank (payment provider).
6DepositDeposit transactions are created with the Deposit API.
7ReclaimReclaim transactions are created with the Reclaim API.
8RepresentmentA representment transaction represents an attempt to reprocess a previously denied Capture transaction.
9Tokenization
10PreauthorizationPreauthorization transactions are created with the Preauthorization API.
11Guarantee

Verification Mode

CodeNameDescription
1VerifiedByMerchant...
2ApprovedByMerchant...
3VerifiedByTrustly...
4AmountAuthorizedByMerchant...

Verification Status

CodeNameDescription
1AutomaticPayment verification followed Trustly internal rules.
2ToVerifyPayment transaction is held (status = OnHold) for further investigation and approval by the merchant.
3VerifiedPayment was verified and approved by the merchant or Trustly (see Verification Mode).
4RefusedPayment was denied by the merchant or Trustly after verification.

Verification Types

CodeNameDescription
0Not VerifiedThe Account was not verified.
1Micro-depositsThe Account was verified using a micro-deposit process.
2Online Banking verificationThe Account was verified using the Trustly Online Banking application.
3Database verificationThe Account was verified using the Trustly database or a Third Party Service.

FCRA Verification Score Values

The table below maps Trustly FCRA Verification score values to a related verified value.

ScoreDescriptionVerified Mapping
0Invalid input. The account or routing number are invalid.false
1There is a strong indication that the account is invalid.false
2There are active non-bankable returns on this account that are less than 3 years old.false
3There are administrative returns on this account.false
4The format appears to be suspicious.false
5There is no data on this account or format.false
6We have not seen this account, but the format appears to be valid.true
7We have seen this account but have not received a final disposition on the transaction.true
8We have seen this account, but not in the last 6 months, and have seen no returns associated with the account.true
9We have seen this account in the last 6 months and have seen no returns associated with the account.true
10This account has been directly validated with/by the financial institution or 3rd party. We have the highest confidence that this account is valid.true

FCRA Verification Third Party Score Values

The table below maps Trustly Verification thirdParty values to a related score value.

ScoreDescriptionVerified Mapping
0Failed RT validation.0
100TeleCheck has a strong indication that this account is invalid.1
200TeleCheck has active non-bankable debt(s) on this account that are less than 3 years old.2
300TeleCheck has administrative returns on this account.3
400TeleCheck does not have Neg data on this account, but the format appears to be suspicious.4
500TeleCheck does not have data on this account or format.5
600TeleCheck has not seen this account, but the format appears valid.6
700TeleCheck has seen this account, but did not receive a final disposition on the transaction.7
800TeleCheck has seen this account, but not in the last 6 months.8
900TeleCheck has seen this account in the last 6 months.9
999TeleCheck has the 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.

ScoreDescriptionVerified Mapping
15Known bad bank account.false
20Unknown bank account, but format appears valid.false
25Unknown bank account, but format appears suspicious.false
35Bank account seen but transaction not yet settled (5 days).true
45Known good bank account.true

Financial Institution Account Type Values

CodeDescription
-1Unknown
0Other
1Checking
2Savings

Financial Institution Account Profile Values

CodeDescription
-1Unknown
0Other
1Personal
2Business

Event Types

TypeIDDescription
Update1This event occurs when only the payment provider transaction status changes and the Trustly transaction status does not change.
Establish2This is the initial event that creates a transaction.
Authorize3This event occurs when the transaction is AUTHORIZED.
Process4This event occurs when the ACH payment instructions are processed by the bank.
Complete5This event occurs when the transaction is considered complete by Trustly. You will be funded for the transaction once this notification is received.
Cancel6This event occurs when the transaction is canceled.
Fail7This event occurs if some error does not allow the transaction to continue.
Expire8This event occurs if the transaction expires before it was completed.
Deny9This event occurs when the payment provider denies the payment.
Refund10This event occurs when a payment transaction is refunded.
Dispute11This event occurs when a payment transaction is disputed.
Reconcile12This event happens if the dispute is settled and the transaction is not reversed.
Reverse13This event occurs if the transaction is reversed (charged back) after being disputed.
Hold14This event occurs when a transaction is put on hold after consumer authorization. This would occur if the ACH gateway were unavailable and will also be used for future risk management
Approve15This event occurs when a transaction that was put on hold due to risk reasons is approved to proceed.
VerifyCustomer16This event occurs when the Verify Customer API is called.
VerifyAccount17This event occurs when the Verify Financial Institution Account API is called.
SendChallenge18This event occurs when a challenged deposit is sent to be processed.
Feedback19This event occurs when service feedback is called by the merchant to report back on what is happening with a transaction of payment type Retrieval, which is authorized by us but is processed by a third party.
FIUser20This event occurs when the Get Financial Institution User is called.
FIAccountBalance21This event occurs when the Get Financial Institution Account Balance API is called.
Reclaim22This event occurs when a deposit transaction is reclaimed.
ChallengeCompleted23This event occurs when the MCD Deposit transactions are completed.
Represent25This event occurs when the transaction is represented by the customer or automatically by PayWithMyBank.
SessionStepStart26
SessionStepComplete27
SessionStepJSError28
Refresh29This event occurs when the merchants call the API to retrieve the updated account balance
Tokenize31This event occurs when the tokenized API is called.
Income32
FIAccountActivity33This event occurs when the merchants call the API to retrieve the account activity.
ReverseEndUserTransaction37This event occurs when receiving a completed notification of a transaction that already failed, indicating it was reversed automatically.
FISelectedAccounts38This event occurs when the merchants call the API to retrieve multiple selected accounts.