Status codes and type definitions

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.

Transaction Status Codes

These codes reflect the current state or reason for failure of a transaction.

Payment Provider Transaction Status Codes (SW)

These status codes relate to errors found during validation before the transaction is sent to the ODFI, covering risk and validation issues.

Status CodeConsumer Decline CodeDescriptionConsumer MessagingSuggested Actions
SW010N/AEstablishedN/AN/A
SW013User CancelledCanceled.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).
SW020N/AAuthorization receivedN/AN/A
SW021Insufficient FundsAuthorization 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.
SW051Merchant ErrorMerchant 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
SW052Bank ErrorFinancial 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
SW053Network ErrorInternal network error.Transaction unsuccessful: We're sorry. The transaction could not be completed because of a technical error from the network.N/A
SW054Security ControlsSuspicious 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.
SW055Security ControlsNegative 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.
SW056Unsupported Account TypeInvalid 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.
SW057Expired Split TokenExpired 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.
SW059Security ControlsInstant transaction rejected due to risk.Security Alert: We detected some unusual activity and as a result, this transaction was not completed.N/A
SW060Bank ErrorBank 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

User Canceled (UC)

These statuses are set when the user cancels the transaction process.

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, generally set when user communication is completed or the merchant calls the API directly.

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)

These statuses indicate internal errors related to system functionality.

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

Return and Decline Codes

Code SetRangeDescription
ACH Return Codes (R)R01 to R84Standard ACH return codes 01 to 84.
EFT Decline Codes (Canada)900 to 996Specific decline codes used for Canadian EFT transactions.
TDD Statuses (UK)ARUCS, ARUDD, AUDDISTrustly direct debit specific return codes for the United Kingdom.

EFT Decline Codes - Canada

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 or Account Mismatch
910Payor or Payee Deceased
911Account Frozen
912Invalid or Incorrect Account No
914Incorrect Payor or Payee Name
915No Agreement Existed - Business or Personal Refused
916Not in accordance with Agreement - Personal
917Agreement Revoked - Personal
918No Confirmation or 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

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

API Response and Internal Error Codes

These codes indicate system-level failures, invalid requests, and security issues encountered during an API call.

HTTP Status Codes

Trustly uses conventional HTTP response codes to indicate success or failure of an API request.

HTTP Status CodeDescription
400 Bad RequestOften due to a missing, required parameter.
401 UnauthorizedInvalid accessId or accessKey.
404 Not FoundThis endpoint is not supported or defined by Trustly.
500 Server errorInternal Trustly error.
503 Service UnavailableThe server is currently unable to handle the request due to temporary overloading or server maintenance.

Internal Error Codes

These codes are returned within the API error response object, providing detail on the failure reason.

Error CodeDescription
100Internal error. An internal database exception occurred when trying to process the request.
150Remote error. A remote error (for example, the consumer's bank interface is down) occurred when trying to process the request.
200Invalid parameter error. One of the request parameters is invalid (for example, sending an invalid amount format string).
210This is a duplicate request. It has been ignored (idempotency failure).
300Security error. A generic security error occurred when trying to process the request.
326Expired split token
330Invalid account
331Not enough balance
375Access control error. Occurs when a security parameter (accessId, accessKey or requestSignature) is invalid.
380Invalid Split Token
390Fraud analysis. Suspicious transaction or negative data.
397splitToken is not valid

Payment Decline Codes and Extended Reasons

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.

Authorization Denied (SW021)

CategoryStatus CodeResponse Description
DeclineSW021Authorization denied

Extended reasons for authorization denied.

Reason CodeExtended Reason CodeExtended Reason DescriptionConsumer Decline Reason Details
12120000Insufficient fundsTransaction 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.

Suspicious Transaction Activity (SW054)

CategoryStatus CodeResponse Description
DeclineSW054Suspicious transaction activity

Extended reasons for suspicious activity declines.

Reason CodeReason DescriptionExtended Reason CodeExtended Reason DescriptionConsumer Decline Reason Details
1Exceeded thresholds10000Exceeded thresholdsSecurity 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.
1Exceeded thresholds10001Exceeded transaction amountSecurity 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.
1Exceeded thresholds11XXXExceeded 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.
1Exceeded thresholds12XXXExceeded 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.
1Exceeded thresholds13XXXExceeded 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.
1Exceeded thresholds14XXXExceeded 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.
2Data mismatch20000Consumer name data mismatchSecurity 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.
2Data mismatch20001Consumer email data mismatchSecurity 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.
2Data mismatch20002Consumer address data mismatchSecurity 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.
3Suspicious History30000Suspicious HistorySecurity 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.
3Suspicious History30101NSF ML risk model: Score higher than thresholdSecurity 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.
3Suspicious History30201NSF risk rules: Hard block based on attributesSecurity 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.
3Suspicious History30301Fraud ML risk model: Score higher than thresholdSecurity 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.
3Suspicious History30401Fraud risk rules: Hard block based on attributesSecurity 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.
43rd Party Suspicious History400003rd Party Suspicious HistorySecurity 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.

Negative Database (SW055)

CategoryStatus CodeResponse Description
DeclineSW055Negative Data
Reason CodeExtended Reason CodeExtended Reason DescriptionConsumer Decline Reason Details
550000Negative DatabaseSecurity 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.
550001Consumer blocklistedSecurity 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.
550002Consumer's device blocklistedSecurity 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.
550003Consumer's bank account blocklistedSecurity 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.
550004Consumer's IP blocklistedSecurity 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.
550005Consumer's geo location blocklistedSecurity 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.
550006Uncollected debt: NSFTransaction 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.
550007Uncollected debt: AdminTransaction 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.
550008Uncollected debt: SUFTransaction 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.
660000Consumer's on sanctions listSecurity 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.
770000Consumer's on IP sanctions listSecurity 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.
880000Consumer blocklisted by 3rd PartySecurity 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.
16160000Unable to communicate reasonTransaction unsuccessful: We're sorry. The transaction could not be completed and no further data is available.

Invalid Account (SW056)

CategoryStatus CodeResponse Description
DeclineSW056Invalid Account
Reason CodeExtended Reason CodeExtended Reason DescriptionConsumer Decline Reason Details
990000Unsupported business bank accountInvalid Account: To comply with Federal, state, or local regulations, Trustly does not currently support this type of account.
10100000Unsupported non-checking bank accountInvalid Account: To comply with Federal, state, or local regulations, Trustly does not currently support this type of account.

Expired Split Token (SW057)

CategoryStatus CodeResponse Description
DeclineSW057Expired Split Token
Reason CodeExtended Reason CodeExtended Reason DescriptionConsumer Decline Reason Details
11110000Expired/Revoked Split TokenTransaction unsuccessful: We're sorry. The transaction could not be completed because of a technical error on the bank's side.
11110001New authentication required due to suspicious activityTransaction unsuccessful: We're sorry. The transaction could not be completed because of a technical error on the bank's side.

Suggested Actions (For Decline Codes)

Response CodeReason CodeSuggested Actions
SW0541Please try again later or use a different bank account.
SW0542Please ensure the user is using their own financial institution that matches with the merchant info.
SW0543Refer to consumer messaging.
SW0544Refer to consumer messaging.
SW05415Please ensure that the beneficiary country is not listed among the prohibited countries for international money transfers.
SW0555Please contact Trustly's merchant support team if the user escalates.
SW0556Refer to consumer messaging.
SW0557Please ensure the user is coming from a non-sanctioned country.
SW0558Please contact Trustly's merchant support team if the user escalates.
SW0569Please prompt the user to use a personal debitable account.
SW05610Prompt the user to use a personal debitable account.
SW05711Please prompt the user to log in again.

Payment and Transaction Data Types

Transaction Status Values (Lifecycle Status)

ValueNameDescription
0NewInitial status after the transaction is created but before the consumer chooses a financial institution for payment.
1PendingConsumer has the Pay Panel open but has not yet authorized the transaction.
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 authorization.
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 (must be done prior to 'Processed' status).
14OnHoldA transaction is put on hold after authorization for merchant approval/investigation.

Payment Provider Types

These codes define the type of bank connectivity or payment instrument used.

CodeDescription
1Online Banking (Direct connection)
2Manual Electronic Check

Payment Types

ValueNameDescription
2DeferredPayment is authorized, but requires a separate Capture API call to debit funds. Multiple captures $\le$ original amount are possible.
3RecurringSame as deferred, but associated with a payment agreement (defines amount/timing of capture).
4DisbursementPayment type used exclusively for mass disbursements.
5VerificationUsed solely to verify the customer account outside of the Trustly system.
6RetrievalData retrieval to fetch account and user information without a payment request.

Transaction Types

ValueNameDescription
0ExternalTransaction created when the Feedback API updates the status of a Retrieval paymentType.
1AuthorizeTransaction created with paymentType is Deferred or Recurring.
2PayTransaction created with paymentType of Instant.
3CaptureCapture transactions are created with the Capture API.
4RefundRefund 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.
8RepresentmentAn attempt to reprocess a previously denied Capture transaction.
9Tokenization
10PreauthorizationPreauthorization transactions are created with the Preauthorization API.
11Guarantee

Risk, Verification, and Account Data

Verification Mode

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

Verification Status

CodeNameDescription
1AutomaticPayment verification followed Trustly internal rules.
2ToVerifyTransaction is held (status = OnHold) pending merchant approval/investigation.
3VerifiedPayment was verified and approved by the merchant or Trustly.
4RefusedPayment was denied 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.

Financial Institution Account Profile Values

These values identify the type of bank account being used.

CodeDescription
-1Unknown
0Other
1Checking
2Savings

Financial Institution Account Type Values

These values define the ownership profile of the bank account.

CodeDescription
-1Unknown
0Other
1Personal
2Business

FCRA Verification Third-Party Score Values (United States)

This table maps Trustly Verification thirdParty values to a related risk score.

ScoreDescriptionVerified Mapping
0Failed RT validation. Strong indication that this account is invalid for payments.0
100Strong indication that this account is invalid for payments.1
200This account has recent non-bankable debts.2
300History of returns on the account.3
400No negative data on this account, but the format appears suspicious.4
500No data on this account or format.5
600Limited information on the account, but the format appears valid.6
700We have seen this account, but did not receive a final disposition on the transaction.7
800We have seen this account but not recently.8
900This account has been seen recently.9
999Highest confidence that this account is valid.10

Non-FCRA Verification Score Values

These scores are used for non-FCRA related risk verification.

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