LOAD_FUNDS
DefinitionCopied!
The LOAD_FUNDS
transaction type is utilized to represent the action of loading money into an account wallet through external payment methods, including both card and bank accounts.
Transaction statusCopied!
The LOAD_FUNDS
transaction supports the following statuses:
Status |
Description |
---|---|
|
Marks the beginning of the transaction in the system. |
|
Signifies approval from the compliance department; the payment process with the bank is underway. |
|
Confirms that the funds have been successfully loaded into the Account Wallet. |
|
The transaction couldn't process, typically due to payment rejection, like a declined card transaction, or an automated risk detection system. |
|
A system glitch or anomaly that hindered the transaction's processing. |
|
Reflects cancellation of the transaction by a fraud detection agent. |
|
An automated system rule resulted in the transaction's cancellation. |
|
The transaction is under detailed review by the Compliance and Fraud department. |
|
The transaction was nullified before the actual payment execution, ensuring no debit or credit on the payment method. |
|
The transaction has been officially declined following a manual review by the Compliance and Fraud department. |
Status reasonCopied!
FAILED status (Bank Payment Method)
For LOAD_FUNDS
Transactions in FAILED
status, when the funds are loaded from a Bank Payment Method, the following status_reasons
are supported:
Status Reason |
Description |
---|---|
|
Insufficient funds in the external bank account when performing a funds balance check |
|
Insufficient funds in the external bank account when performing a funds balance recheck for fraud prevention |
|
Error when performing when performing a funds balance recheck for fraud prevention |
|
Previous transaction(s) returned, causing authorization failure for current transaction |
|
Public token used for transaction is invalid or expired |
|
Access token for external bank account is invalid or expired |
|
The account ID of the external bank account is incorrect or unrecognized |
|
Failure in mapping exchange tokens during the transaction process |
|
The bank account details provided are invalid or do not match with the external bank |
|
The external bank account or its features are not supported by the platform |
|
The external bank account is temporarily locked or restricted |
|
The external bank account could not be verified for the transaction |
|
Exceeded the number of allowed verification attempts for the external bank account |
|
No external bank accounts are linked or available for the transaction |
|
No valid checking or savings account(s) for which account and routing numbers could be retrieved |
|
No valid investment account(s) for which holdings or transactions could be retrieved |
|
The specified external bank account was not found |
|
The last updated balance of the external bank account is outside the permissible range for the transaction |
|
The transaction could not be authorized because we were unable to verify the account's balance. Additionally, the most recent balance information we have indicates that the funds in the account fall short of the minimum required by our risk assessment model |
|
The frequency of balance inquiries for the external bank account has exceeded the platform's limits |
|
The failure reason is not specifically identified or mapped |
FAILED status (Card Payment Method)
For LOAD_FUNDS
Transactions in FAILED
status, when the funds are loaded from a Card Payment Method, the following status_reasons
are supported:
Status Reason |
Description (Revised) |
---|---|
|
Transaction declined by the issuing bank |
|
Merchant or provider involved in the transaction is invalid or unrecognized |
|
Authorization for the transaction was declined |
|
Failure reason not specified or falls under miscellaneous |
|
The transaction request is still being processed |
|
Transaction partially approved, indicating partial or incomplete transfer |
|
Transaction is invalid due to errors in transaction details or format |
|
The amount specified in the transaction is invalid or incorrect |
|
The account number of the card is invalid or unrecognized |
|
Transaction cancelled by the customer |
|
Transaction disputed by the customer |
|
Error in the transaction format or data |
|
Transaction only partially completed |
|
No credit account associated with the card available for the transaction |
|
No investment account available for the transaction |
|
Insufficient funds available in the card's account |
|
No checking account associated with the card available for the transaction |
|
No savings account associated with the card available for the transaction |
|
The card used for the transaction has expired |
|
No record of the card found in the system |
|
Transaction type not permitted for the cardholder |
|
Transaction flagged as suspected fraud |
|
Card acceptor needs to contact the acquirer |
|
Transaction amount exceeds the card's maximum activity limit |
|
The card is restricted and cannot be used for the transaction |
|
Transaction flagged due to security concerns |
|
Transaction exceeds the card's withdrawal frequency limit |
|
Late response in processing the transaction |
|
The card used is not active or has not been activated for use |
|
Failure in verifying the card's CVV2 code during the transaction |
|
Transaction requires the card's PIN, which was not provided or incorrect |
|
Transaction exceeds the card's daily amount limit |
|
Transaction exceeds the card's transaction limit |
|
The card type or network is not supported by the platform |
|
The currency involved in the transaction is not supported |
|
Transaction exceeds the merchant's transaction limit |
|
Card not enrolled in 3D Secure for the transaction |
|
3D Secure authentication failed during the transaction |
|
3D Secure authentication expired prior to transaction completion |
|
Issue encountered with the 3D Secure system |
|
3D Secure authentication is required for the transaction |
|
Error occurred during 3D Secure processing |
|
Notification to retrieve the card, usually due to suspected fraud or security issues |
|
The issuer of the card could not be identified or found |
|
Transaction exceeds the maximum amount limit set by the card issuer |
|
Transaction declined by the card issuer for unspecified reasons |
|
Exceeded the maximum PIN entry attempts, suspected fraud |
|
Transaction attempted with a card reported lost |
|
Transaction attempted with a card reported stolen |
|
Transaction declined due to Anti-Money Laundering Directive 5 compliance issues |
|
Transaction attempted with a card linked to a closed account |
|
The card or cardholder is blacklisted, preventing transaction completion |
|
Transaction flagged as potentially fraudulent. Contact the card issuer for further verification. |
|
The card issuer must be contacted for further details or authorization. |
|
Merchant is not recognized or authorized by the card network. |
|
Transaction attempted with a card reported as stolen. Immediate blocking and investigation required. |
|
The card issuer declined the transaction without providing further details. |
|
A general error occurred in the transaction processing, requiring a retry or further investigation. |
|
The card is suspected to be compromised and should be retained by the merchant. |
|
Transaction requires identity verification of the cardholder to proceed. |
|
Only a partial amount of the transaction was approved by the card issuer. |
|
The provided card number is invalid or does not match any card issuer. |
|
Transaction needs to be entered again due to an error or miscommunication. |
|
The response from the card network was invalid or incomplete. |
|
The requested action was not taken, possibly due to a previously processed transaction. |
|
A technical malfunction suspected, preventing transaction completion. |
|
The transaction fee exceeds the allowed limit by the card issuer or network. |
|
The requested file update operation is not supported by the system. |
|
The requested record for the transaction could not be found. |
|
A duplicate file update request was detected and rejected. |
|
An error in one of the fields in the file update request was detected. |
|
The record intended for update is locked and cannot be updated at the moment. |
|
Update attempt to the file containing card data was unsuccessful, possibly due to system error or network issues. |
|
The bank associated with the card is not supported by the payment network or merchant's system. |
|
The transaction was only partially completed, possibly due to insufficient funds or credit limit restrictions. |
|
Transaction attempted with an expired card, suspected of fraud. |
|
Merchant must contact the acquirer due to a suspicious transaction that could be fraudulent. |
|
Card has been restricted due to suspected fraudulent activities. |
|
The requested action is not supported by the card, network, or issuer. |
|
No universal account number could be found or matched, typically in systems requiring cross-border compatibility. |
|
Transaction attempted on an account that has been previously closed. |
|
Insufficient funds in the cardholder's account to complete the transaction. |
|
The entered PIN does not match the PIN stored on record for the card. |
|
The specified card number could not be found in the issuer's system. |
|
The cardholder's account does not permit this type of transaction. |
|
The amount requested exceeds the withdrawal limit set for the card or account. |
|
The card has been restricted, possibly for security or administrative reasons. |
|
The amount initially authorized differs from the amount being charged. |
|
Merchant must contact the acquirer due to security concerns potentially involving the transaction. |
|
Card must be physically retained by the merchant due to suspected fraud. |
|
The allowable number of PIN entry attempts has been exceeded, triggering a security response. |
|
There was an error in synchronizing the encryption keys used in the transaction. |
|
The Point of Sale terminal used is not eligible for this transaction, possibly due to settings or network restrictions. |
|
Transaction declined due to the card being at a lifecycle stage that does not permit the transaction (e.g., expired, not activated). |
|
Transaction attempted with a date that is no longer valid or too old as per issuer's policies. |
|
Issuer's systems are possibly down, and a stand-in authorization is requested, but not possible. |
|
Transaction flagged for security review due to potential fraud indicators or violation of security protocols. |
|
Transaction exceeds the time limit set for completing a transaction following a pre-authorization. |
|
Issuer declined the transaction without providing any specific reason. |
|
The entered PIN could not be verified as correct by the card issuer or network. |
|
A transaction similar to the current one has already been processed and posted. |
|
Required information for processing the transaction is missing from the issuer's records. |
|
The Card Verification Value (CVV) entered is incorrect or invalid. |
|
Transaction attempted during a processing cutoff period, typically end of day or batch processing time. |
|
The card issuer or payment switch is temporarily inoperative or under maintenance. |
|
The transaction was sent to an unrecognized network, or there's an error identifying the network. |
|
Transaction stopped due to a suspected violation of law or regulation. |
|
The same transaction has been submitted more than once. |
|
An error occurred during the reconciliation process, possibly due to mismatched transaction details. |
|
A general system malfunction occurred, preventing the transaction from being processed. |
|
Code reserved for specific national use cases, not applicable or unrecognized in the current context. |
|
A failure or fault has been detected in the card network, affecting transaction processing. |
|
General network-related issues preventing successful transaction processing. |
|
Security measures required for the transaction are invalid or not supported by the current system setup. |
|
Address Verification Service (AVS) data was not provided but is required for processing the transaction. |
|
Card Verification Value (CVV2) is required but was not provided or was incorrect. |
|
The transaction is blocked because the issuer's country is on a blocked list. |
|
Message Authentication Code (MAC) was incorrect, suggesting a data integrity issue. |
|
The transaction does not meet the standard entry class requirements, often related to batch processing rules. |
|
The transaction could not be processed in time, leading to a timeout. |
|
The provided account number does not meet the required length for processing. |
|
The check digit for the account number is incorrect, failing validation. |
|
Card Identification Number (CID) format is incorrect or invalid. |
|
The authorization for the transaction has expired before completion. |
|
The card product code does not match the transaction type or is not supported. |
|
There is a mismatch between the transaction and the BRIC (Biometric Risk Identification Code) PIN data. |
|
Transaction processing timed out specifically on the CyberSource payment gateway. |
|
Essential information required for processing the transaction is missing. |
|
The card number is not valid or does not exist. |
|
The required PIN block was not present in the transaction data. |
|
The BIN necessary for routing the pinless transaction is missing. |
|
The signature required to complete the transaction was not fully captured or stored. |
|
Error in swipe data processing for a debit transaction requiring PIN verification. |
|
Database timeout occurred, preventing transaction completion. |
|
The transaction was declined by the merchant, possibly due to policy or suspecting fraud. |
|
There was an error in routing the transaction through the payment gateway. |
|
The authorization provided was not accepted by the processing network or issuer. |
|
The transaction was flagged because the item or service was not received by the purchaser. |
|
The transaction amount exceeds the floor limit for transactions without additional authorization. |
|
The issuer declined the authorization request without specifying the reason. |
|
The account number provided does not match any account on record. |
|
An addition error occurred in the transaction processing, possibly due to a computational or data entry error. |
|
The amount authorized differs from the amount charged, suggesting alteration. |
|
The account number entered is incorrect or does not match the expected format. |
|
A required signature for the transaction is missing, necessary for verification or authorization. |
|
The transaction slip lacks a card imprint, required for physical verification in some manual transactions. |
|
Multiple card imprints on a single slip, indicating a potential error or fraud attempt. |
|
A pre-authorization was canceled before the transaction could be completed, possibly by the cardholder or issuer. |
|
Errors occurred in converting currency values during the transaction processing. |
|
A transaction intended as a credit was processed as a debit, causing accounting errors. |
|
The transaction was disputed by the cardholder, initiating a claim or defense process. |
|
The goods or services were not received by the cardholder, leading to a transaction dispute. |
|
Goods received were defective, leading to a transaction dispute. |
|
Failure in the card authentication process, possibly due to incorrect data or security breaches. |
|
Transaction identified as fraudulent by systems or manual review. |
|
The merchant involved in the transaction has been blocked from processing payments due to compliance issues or fraud. |
|
Incorrect CVV3 code entered, a security measure on the card that was not matched correctly. |
|
An error occurred for which the cause is not specified or unknown. |
|
A check presented for cashing was not acceptable, possibly due to issues with the check or bank policies. |
|
The check used for the transaction was not accepted by the merchant or bank. |
|
The amount of the check exceeded the deposit limit set by the bank or merchant. |
|
The requested cashback exceeds the limit set by the merchant or bank. |
|
The written and numerical amounts on a check do not match, commonly referred to as a courtesy amount error. |
|
The PIN for the transaction was not selected or set up by the cardholder. |
|
An attempt was made to select or change a PIN that had already been established. |
|
The voucher presented does not match records or expected values for the transaction. |
|
The number of allowed attempts to enter the card number (PAN) has been exceeded during the transaction. |
|
The expiration date entered is incorrect or past due. |
|
The card is inactive either due to not being activated or having been deactivated by the issuer. |
|
Incorrect expiration date used as a potential fraud attempt. |
|
A stop payment order suspected on an item involved in the transaction. |
|
The transaction amount is ineligible for processing under current policy or limits. |
|
The same item has been submitted for payment more than twice, indicating a possible error or fraud. |
|
No account was found corresponding to the information provided in the transaction. |
|
The transaction details or related records could not be located in the system. |
|
A general denial without specific details, often used when specific error codes are not applicable. |
|
The transaction was settled through Automated Clearing House (ACH), not directly through card networks. |
|
Settlement was delayed beyond the acceptable period, often leading to transaction failure. |
|
The card details do not match any records in the cross-reference file, possibly due to a data mismatch or outdated information. |
|
The transaction exceeds the spending limit set for a specific category of purchases. |
|
The amount or number of transactions exceeds the daily limit set by the issuer or bank. |
|
The transaction amount or count goes beyond the set monthly limit for the account. |
|
The secret code entered (like a PIN or a password) was invalid. |
|
There is a synchronization issue with the PIN key, possibly due to technical errors in encryption or communication. |
|
The CVV2 code entered was incorrect, failing security verification required for transaction processing. |
|
A stop payment order has been issued on this transaction or on the instrument used. |
|
The authorization previously granted for the transaction has been revoked by the cardholder or issuer. |
|
Recurring payments have been stopped at the request of the cardholder or due to a policy violation. |
|
The transaction was declined because the card was reported lost. |
|
The account associated with the card is dormant due to inactivity, triggering security protocols that block transactions. |
|
The transaction was flagged due to special conditions set on the account or card, requiring further checks or validation. |
|
The transaction is permitted only if it includes a cashback component, otherwise, it's declined. |
|
There are insufficient funds in the account to cover the fees associated with the transaction. |
|
The transaction failed ARQC (Application Request Cryptogram) validation, indicating possible tampering or data corruption. |
|
The PIN used is considered unsafe (e.g., too simple or compromised) and has triggered a security block. |
|
The transaction was declined because the MasterCard used has expired. |
|
MasterCard has declined the transaction for reasons not specified to the merchant. |
|
The BIN (Bank Identification Number) on the MasterCard is not supported by the processing network. |
|
The transaction was declined by MasterCard for an unknown reason, requiring further investigation. |
|
The status of the transaction is unknown due to an issue with MasterCard's processing. |