Error codes
With the Visa/Mastercard credit cards, you tin can trigger specific error codes past using the transaction amounts given in the column "Examination amount"
Operation failed
| Result Code | Issue Message | More than information | Test corporeality |
| 001999 | Generic Operation fault | An incident or connection issue has occured and airtight all transactions. | |
| 001001 | Unsufficient wallet residual | The e-wallet does not contain enough funds to process the transaction | |
| 001002 | Writer is not the wallet possessor | The user ID used every bit Author has to be the wallet possessor | |
| 001011 | Transaction amount is higher than maximum permitted corporeality | | |
| 001012 | Transaction corporeality is lower than minimum permitted amount | | |
| 001013 | Invalid transaction amount | The user's bank has rejected the transaction. Users should contact his/her banking company for more information. | 333.13 |
| 001014 | CreditedFunds must be more than than 0 (DebitedFunds can not equal Fees) | | |
PayIn Web errors
| Effect Code | Issue Message | More information |
| 001030 | User has not been redirected | The user never gets the payment page and never opens the Payline session |
| 001031 | User canceled the payment | The User clicks on "Cancelled" on the payment page |
| 101002 | The transaction has been cancelled past the user | The User clicks on "Cancelled" on the payment folio |
| 001032 | User is filling in the payment carte du jour details | The user is still on the payment folio (Payline session) |
| 001033 | User has non been redirected then the payment session has expired | The session has expired and then the Payin Web is failed. The user has gone on the payment page |
| 001034 | User has let the payment session elapse without paying | The user went to the payment page but let the session expired. Then the Payin Web has failed |
| 101001 | The user does not complete transaction | The user did not enter some of the compulsory information. All fields should be completed inside the first minutes of payment. |
Refund transaction errors
| Result Lawmaking | Result Message | More information |
| 001401 | Transaction has already been successfully refunded | |
| 005403 | The refund cannot exceed initial transaction corporeality | Refunding more than the initial transaction'southward value is not possible. Make a divide transfer to add a bounty. |
| 005404 | The refunded fees cannot exceed initial fee amount | Refunding more than the initial transaction fee is not possible. Make a separate transfer to add a compensation. |
| 005405 | Residuum of client fee e-wallet bereft | Fees cannot be included in a refund if the fee due east-wallet has already been debited and that the outstanding amount has been payed out. |
| 005407 | Duplicated operation: you cannot refund the same corporeality more than than once for a transaction during the aforementioned day | Refunds processed twice for the aforementioned amount on a specific transaction are blocked to prevent unintentional double-refunds. |
| 001403 | The transaction cannot exist refunded (max 11 months) | |
Card input errors
| Consequence Code | Issue Message | More information | Test amount |
| 105101 | Invalid carte number | The card number given doesn't friction match the real number of the card | 333.14 |
| 105102 | Invalid cardholder name | The bill of fare holder name given doesn't match the real owner of the card | |
| 105103 | Invalid PIN code | The Personal Identification Number lawmaking is invalid. The user should bank check card information and retry. | 333.55 |
| 105104 | Invalid PIN format | The Personal Identification Number format is invalid. The user should check bill of fare information and retry | |
Transaction Refused
| Issue Code | Issue Message | More than information | Test corporeality |
| 101101 | Transaction refused by the banking concern (Do non honor) | The error "Do not honor" is a message from the bank. Yous could get it for several raisons: Maximum amount spent per month has been reached on this card // Maximum amount spent on cyberspace per calendar month has been reached on this card // No more funds on bank account | 333.05 (or utilise the CVV code 999) |
| 101102 | Transaction refused past the banking concern (Amount limit) | You will go this error if the user reached a bank corporeality limit. It could exist: Maximum pre authorized amount reached // Maximum amount spent per month has been reached on this carte // Maximum amount spent on internet per month has been reached on this card | 333.51 |
| 101103 | Transaction refused by the last | The concluding refusal may be linked to the user's card. The user should try to use an culling card/payment method. | 333.58 |
| 101104 | Transaction refused past the bank (card limit reached) | | 333.60 |
| 101105 | The card has expired | | |
| 101106 | The card is inactive | The bill of fare is not active accourding to the banking company and can therefore not be used | |
| 101108 | Transaction refused: the Debited Wallet and the Credited Wallet must be dissimilar | Funds cannot exist transferred to the aforementioned e-wallet. Try to move the funds to a different e-wallet. | |
| 101109 | The payment period has expired | Bankwires payin expire after i calendar month if the funds has not been received by MANGOPAY within this time | |
| 101110 | The payment has been refused | Due to a bank wire issue, the bank transfer has been declined or cancelled. Please attempt over again. | |
| 101410 | The bill of fare is not active | The card has been disabled on Mangopay and is no longer useable | |
| 101111 | Maximum number of attempts reached | Likewise much attempts for the same transaction | 333.38 |
| 101112 | Maximum amount exceeded | This is a card limitation on spent amount | |
| 101113 | Maximum Uses Exceeded | Maximum attempts with this cards reached. You must try again after 24 hours | |
| 101115 | Debit limit exceeded | This is a card limitation on spent amount | 333.61 |
| 101116 | Amount limit | The number of authorised daily transactions has been exceeded. Delight contact our back up to adjust the number of daily transactions. | |
| 101118 | An initial transaction with the same card is still pending | | |
| 002996 | Blocked due to User Rest limitations (maximum owned amount reached) | | |
| 101199 | Transaction refused | The transaction has been refused by the bank. Contact your bank in order to have more data virtually it | |
| 205001 | Paypal Information validation mistake | Delight ensure that you are sending the right data. One of the required parameters may exist either missing or invalid. | |
SecureMode / 3DSecure errors
| Effect Code | Consequence Message | More information |
| 101399 | SecureMode: 3DSecure authentication is not available | 3DSecure is not available. Please contact our support to unblock the state of affairs. |
| 101304 | SecureMode: The 3DSecure authentication session has expired | |
| 101303 | SecureMode: The menu is non compatible with 3DSecure | |
| 101302 | SecureMode: The card is not enrolled with 3DSecure | |
| 101301 | SecureMode: 3DSecure authentication has failed | |
| 101305 | SecureMode: Soft turn down | Strong client authentication is required in order to exist able to continue to payment |
| 101306 | SecureMode: 3DSecure authentication requested | |
Tokenization / Card registration errors
| Consequence Code | Upshot Message | More than information |
| 001599 | Token processing error | The token has not been created as in that location was a problem - check that yous sent all the correct parameters. |
| 105299 | Token input Mistake | This is a generic mistake meaning that we got an error when submitting the token to the bank. It is usually returned because there was a besides long fourth dimension between the card registration request and the first action washed with this bill of fare. Indeed, yous have 20min maximum to create the first Pre-auth or Payin |
| 105202 | Carte number: invalid format | This mistake is returned in example the card number formate is wrong (on menu registration) |
| 105203 | Death date: missing or invalid format | This fault is returned in case the expiry date is wrong (on bill of fare registration) |
| 105204 | CVV: missing or invalid format | This mistake is returned in case the CVV is wrong (on carte du jour registration) |
| 105205 | Callback URL: Invalid format | This mistake is returned in case the ReturnURL is wrong on CardRegistration process |
| 105206 | Registration information : Invalid format | This error is returned in case the information sent to the tokenization server is non the right. You can get this mistake when yous are trying to edit the CardRegistration Object with the RegistrationData(got from the tokenization server) |
The following errors may be received by our PSP when POSTing the carte du jour data to the CardRegistrationURL
| Result Code | Result Bulletin | More information | Test amount |
| 02625 | Invalid card number | | |
| 02626 | Invalid date. Utilize MMYY format | | |
| 02627 | Invalid CCV number | | |
| 02628 | Transaction refused | Invalid URL return field | |
| 02101 | Internal Mistake | At that place is an issue on the tokenization server (PSP side). Please bank check the resolution on http://status.mangopay.com/ | |
| 02632 | Method Go is not allowed | Your Payment form has to use POST method on Tokenization Server | |
| 09101 | Username/Password is incorrect | Please ensure that you are sending the right registration data. | |
| 09102 | Account is locked or inactive | | |
| 01902 | This carte du jour is not active | | 333.12 |
| 02624 | Card expired | | 333.33 |
| 09104 | Client certificate is disabled | | |
| 09201 | Yous do not take permissions to make this API call | | |
| 02631 | Filibuster exceeded | Too much time taken from the creation of the CardRegistration object to the submission of the Card Details on the Tokenizer Server | |
Specific JS Kit card registration errors
| Result Code | Outcome Message | More data | Test amount |
| 009999 | Browser does not support making cross-origin Ajax calls | | 333.57 |
| 001596 | An HTTP asking was blocked by the User's antivirus | Getting the token from Payline failed due to the HTTP call beingness blocked by an anti-virus/plugin/extension - for example, this is known to happen with Kaspersky if the "Safe Money" choice is activated | |
| 001597 | An HTTP asking failed | | |
| 001598 | A cross-origin HTTP asking failed | | |
| 001599 | Token processing mistake | Getting the token from Payline failed as no token data was received - most likely, the HTTP call failed for some reason - a timeout or anti-virus/plugin/extension may have blocked it | |
| 101699 | CardRegistration should return a valid JSON response | Finishing card registration with MANGOPAY API failed as a valid JSON response wasn't received for some reason | |
| 105204 | CVV_FORMAT_ERROR | The CVV is missing or not the required the length | |
| 105203 | PAST_EXPIRY_DATE_ERROR or EXPIRY_DATE_FORMAT_ERROR | The expiry date is not in the future | |
| 105202 | CARD_NUMBER_FORMAT_ERROR | The bill of fare number is not a valid format | |
Transaction fraud issue
| Event Code | Result Message | More information | Test amount |
| 008999 | Fraud policy error | | |
| 008001 | Counterfeit Card | Fake card detected by the bank. The user should contact his/her bank to unblock the situation. | |
| 008002 | Lost Card | A "lost carte du jour" error is a rule carried by the banking concern which deactivate a card due to as well many payments (or attempts). In Sandbox, just choose another carte du jour, this one will be reactivated soon (the twenty-four hour period after). In Production, the card is blocked for the day or concidered as fraudulent by the bank | 333.41 |
| 008003 | Stolen Card | Like to 008002 | 333.43 |
| 008004 | Bill of fare bin not authorized | This bill of fare has been blocked by our fraud section. Please contact our support team or use a different card | |
| 008005 | Security violation | This carte has abnormal behavior and has been blocked by our fraud section. Please contact our back up or use a different menu. | 333.63 |
| 008006 | Fraud suspected by the bank | This card has abnormal beliefs and has been blocked by our fraud department. Delight contact our back up or use a different menu. | 333.34 |
| 008007 | Opposition on banking concern business relationship (Temporary) | The carte has temporarily been blocked on our side. Please try again later | |
| 008500 | Transaction blocked by Fraud Policy | This payment does not comply with our anti-fraud rules. Delight contact our support team to solve the issue. | |
| 008501 | Transaction refused due to blocked State | The payout cannot exist performed considering the target state is not authorized | |
| 008502 | Transaction refused due to blocked IBAN | The payout cannot exist performed because the target bank business relationship is not authorized | |
| 008503 | Transaction refused due to blocked BIC | The payout cannot be performed because the target bank is not authorized | |
| 008504 | Corporeality of the transaction exceeded the amount permitted | | |
| 008505 | Number of accepted transactions exceeded the velocity limit fix | Credit/debit cards are express to 10 payments per day for security reasons. Please try once again in 24 hours. | |
| 008506 | Unauthorized IP address state | | |
| 008507 | Cumulative value of transactions exceeded | | |
| 008508 | Unauthorized Card issuer country | | |
| 008509 | Number of banking concern cards allowed is exceeded | | |
| 008510 | Number of clients per card is exceeded | | |
| 008511 | The 3DSecure authentification has failed due to supplementary security checks | Anti-fraud rules have triggered a supplementary 3DSecure authentication and this hallmark has failed | |
| 008512 | IP location different than carte du jour issuer country | | |
| 008513 | Number of device fingerprints allowed is exceeded | | |
| 008514 | Unauthorized Bill of fare BIN | | |
| 008515 | Authentication non available: do non benefit from liability shift | 3DSecure is non bachelor on this transaction. Liability shift has been rejected by the issuing banking company. The user should contact his/her bank to solve this trouble and allow the liability shift. | |
| 008600 | Wallet blocked by Fraud policy | | |
| 008700 | User blocked by Fraud policy | This user does not comply with our anti-fraud rules. Please contact our support team to solve the effect. | |
Technical errors
| Event Code | Result Bulletin | More information | Test amount |
| 009103 | PSP configuration error | | 333.03 |
| 009199 | PSP technical mistake | The mistake lawmaking is returned in the following cases: - Card is not supported by Mangopay
- Corporeality is higher than the maximum corporeality per transaction
- Functioning doesn't fit to your Mangopay account settings
- Utilise of a non-3DSecure test carte du jour for a payment which requires 3DSecure
| 333.94 |
| 009499 | Depository financial institution technical error | The Bank has denied the payment for unknown reasons. The user should contact his/her banking concern for more data. | 333.91 |
| 009999 | Technical error | | |
| 009101 | PSP timeout please attempt later | | |
| 101202 | Bank not supported for Giropay | The user'south bank does non back up Giropay payments. | |
Payout error codes
- If your payout is successfully treated (your payout becomes SUCCEEDED), it tin later on exist reaccredited for a variety of reasons.
- In this example, the payout stays equally "SUCCEEDED" but a new transaction is created, which will be a Refund of the original Payout (in the same manner you can have a refunded Payin except the departure is that its not client driven).
- In this case, as for payin refunds, you'll have two fields within
RefundReason -> RefundReasonMessage and RefundReasonType. Possible RefundReason are: BANKACCOUNT_INCORRECT, BANKACCOUNT_HAS_BEEN_CLOSED, OWNER_DOT_NOT_MATCH_BANKACCOUNT, WITHDRAWAL_IMPOSSIBLE_ON_SAVINGS_ACCOUNTS. This will usually be accompanied by a custom message in the RefundReasonMessage field
| Result Lawmaking | Issue Message | More information |
| 121999 | Generic withdrawal error | -------- |
| 121001 | The banking concern wire has been refused | The bankwire has been refused by MGP or cancelled by the user. Y'all should contact us to unblock the state of affairs and allow the bankwire towards MGP. |
| 121002 | The author is non the wallet owner | -------- |
| 121003 or 001001 | Insufficient wallet balance | -------- |
| 121004 | Specific case: please contact our Back up Team | -------- |
| 121005 | Refused due to the Fraud Policy | -------- |
| 121006 | The associated bank account is not active | -------- |
| 121007 | The writer is not the bank account possessor | -------- |
| 002998 | Blocked due to the Depository financial institution Account Owner's KYC limitations (maximum debited or credited amount reached) | The banking concern account needs to be KYC verified (more info) |
| 002999 | Blocked due to a Debited User's KYC limitations (maximum debited or credited corporeality reached) | One of the user's who has contributed to the wallet being debited needs to be KYC verified (more info) |
| 130001 | The client's settings are incorrectly configured for instant payout | -------- |
| 130002 | The amount requested is greater than the authorised corporeality | Threshold activation: the amount requested is greater than the instant payment threshold. On-need activation: the amount requested is greater than the threshold above which MANGOPAY carries out a manual verification. |
| 130003 | The user is not KYC validated | -------- |
| 130004 | The user is blocked by MANGOPAY's fraud policy | -------- |
| 130005 | One or more required parameters are missing or incorrect. An incorrect resource ID also produces this kind of error | For example, the BankAccount address is not a sub-object (v2.01), or there are incorrect or missing parameters in the body. |
| 130006 | Technical error; please try again afterward | -------- |
| 130007 | The destination bank is not reachable | -------- |
| 130008 | Duplicate transaction identified | Instant payouts are express to one instant payout of the same amount to the aforementioned bank account per 24 hours. |
| 130009 | The destination IBAN is not valid | -------- |
| 130010 | Generic operation error | -------- |
KYC certificate errors
In example we could not validate a KYC certificate, yous may be able to obtain more data almost the reason why via two parameters returned by the API when yous telephone call the endpoint View a KYC Certificate.
Identity proof
- For the document type
IDENTITY_PROOF , the parameter Flags may contain one or more error codes, which are explained below.
| Flags | Description |
| 009000 | The document is suspected to be fraudulent : - The account will remain blocked until reception of a valid ID proof (document with better visual quality or a different ID proof)
- Our Fraud team is checking all related transactions
|
| 009001 | Fonts of the document don't match the expected ones |
| 009002 | Picture of person is altered |
| 009003 | Document is partially or totally covered |
| 009004 | Document is blurred |
| 009005 | Cut-off certificate (MRZ ring, …) |
| 009006 | Glare on photo. Please make sure to submit a perfectly readable document without a flash on information technology. |
| 009007 | Incorrect side of the document was submitted |
| 009008 | Ii different documents were uploaded at the aforementioned time |
| 009009 | Please contact our Support squad |
| 009010 | No document in paradigm |
| 009011 | Photo is likewise dark |
| 009012 | Document is damaged |
| 009013 | A punched hole is present |
| 009014 | Corner has been physically cut off, delight make sure certificate is valid |
| 009015 | Certificate contains severely diminished colours |
| 009016 | Glare obscuring a security scrap |
| 009017 | Some features are obscured, please cheque your document quality |
| 009018 | Back of document is needed for processing |
| 009019 | Mangopay currently does not support that type of document. Please come across our listing of supported documents here |
| 009020 | Document owner is nether the historic period of 18 years old |
| 009021 | Document has expired. Please make sure to submit an up-to-appointment certificate |
| 009022 | first_name does non match between declared information and extracted information. - For a Natural User, declared FirstName must match with the firstname extracted from ID document
- For a Legal User, declared LegalRepresentativeFirstName must match with the firstname extracted from ID document
|
| 009023 | last_name does not lucifer betwixt declared data and extracted information. - For a Natural User, declared LastNameName must match with the lastname extracted from ID document
- For a Legal User, declared LegalRepresentativeLastName must match with the lastname extracted from ID document
Notation that for French ID document we do support spouse_name, widow_name or alias_name as alleged LastName (or LegalRepresentativeLastName) |
| 009100 | Please contact our Support squad for a farther explanation about the issue |
Legal documents
- For the document types
REGISTRATION_PROOF, ARTICLES_OF_ASSOCIATION, and SHAREHOLDER_DECLARATION the RefusedReasonType may contain farther data. Additional information may also exist bachelor in the parameter RefusedReasonMessage.
| Refused Reason Blazon | REGISTRATION_PROOF | ARTICLES_OF_ASSOCIATION | SHAREHOLDER_DECLARATION |
| DOCUMENT_UNREADABLE | A clear copy of your Up-to-date Extract from the Companies Register is required. The one provided is not articulate enough | A clear copy of Upward-to-appointment Articles of Clan is required. The one provided is not clear plenty | A clear copy of Up-to-date shareholder declaration is required. The one provided is not clear plenty |
| DOCUMENT_NOT_ACCEPTED | Document is not acceptable, it doesn't fit the KYC requirements guideline agreed with us | Document is non acceptable, it doesn't fit the KYC requirements guideline agreed with the states | Certificate is non acceptable, it doesn't fit the KYC requirements guideline agreed with us |
| DOCUMENT_HAS_EXPIRED | - Document is outdated (more than three months)
- A recent copy of Up-to-date Extract from the Companies Annals is required (maximum iii months old)
| - Document is outdated
- A copy of Upwardly-to-date and signed Articles of Association (which include the last modifications made) is required
| North/A |
| DOCUMENT_INCOMPLETE | - A recent copy of Upwards-to-date Extract from the Companies Annals is required
- All the pages of the document need to be provided
- Delight add together to this extract, the extract of the company president in order to identify the legal representative registered
| - The full copy of the Up-to-engagement Manufactures of Association is required (all the pages signed of the document demand to exist provided)
- Delight resubmit this document together with the statutes of the association in the same package. The registered legal representative does non seem to be one of the persons authorised to represent the association
- Please resubmit these articles of clan together with the latest minutes of the General Assembly stipulating the electric current officers of the clan, every bit nosotros cannot identify the registered legal representative.
| - Date, proper noun or signature is missing
- Document was left blanked
- Missing data in the table
- Important to know who INDIRECTLY own the company if a holding company has the first level ownership
|
| DOCUMENT_MISSING | | | |
| DOCUMENT_DO_NOT_MATCH_USER_DATA | We cannot place the legal representative registered, please go on to the alter or submit a proxy with this extract | - The company or organization indicated on the document does not stand for to the ane registered
- For oganization, please alter the registered legal representative to a natural person authorised to represent the clan (president, secretarial assistant, treasurer)
| - The company / arrangement indicated on the certificate does not correspond to the 1 registered
- The informations submitted do not match with the Articles of Association
|
| SPECIFIC_CASE | Depends on the specific bulletin | Depends on the specific message | Depends on the specific message |
| DOCUMENT_FALSIFIED | The information on the document seems to be fraudulent or inconsistent | The information on the document seems to be fraudulent or inconsistent | The information on the document seems to be fraudulent or inconsistent |
| UNDERAGE_PERSON | | | |
UBO declaration errors
- When an UBO declaration is INCOMPLETE, it is possible to change / add information.
- When information technology is in REFUSAL : it will be necessary to make a new UBO declaration.
| Refused Reason Blazon | More than information |
| MISSING_UBO | We miss some people in you announcement. ex: in the statutes we have ii shareholders having 50% and 50%, if merely ane is indicated, it is a missing UBO |
| WRONG_UBO_INFORMATION | Proper name, get-go proper noun, or other parameters are incorrectly entered. |
| UBO_IDENTITY_NEEDED | We need the UBO ID. |
| SHAREHOLDERS_DECLARATION_NEEDED | The statutes are silent, then we cannot verify if the information provided in the UBO is correct: We need a shareholder declaration certificate |
| ORGANIZATION_CHART_NEEDED | In case of a complex holding compages we need the system nautical chart |
| DOCUMENTS_NEEDED | We are waiting the statutes and / or proof of registration to verify that all is correct. |
| DECLARATION_DO_NOT_MATCH_UBO_INFORMATION | The data provided does not match the information we have on the UBO. |
Mandates errors
The table below lists the range of statuses that tin can exist applied to a Straight Debit mandate, forth with the corresponding description of when that status applies.
| Consequence Code | Result Bulletin | More information |
| 001801 | The depository financial institution account has been closed | |
| 001802 | The depository financial institution details supplied were incorrect | |
| 001803 | Direct debit is not enabled for this banking company business relationship | |
| 001804 | The user has disputed the authorisation of the mandate | |
| 001805 | The user has cancelled the mandate | |
| 001806 | The client has cancelled the mandate | |
| 001807 | User has permit the mandate session expire without confirming | |
| 001024 | Author is non the Mandate owner | |
| 001830 | There are bereft funds in the bank business relationship | |
| 001831 | Contact the user | |
| 001832 | The payment has been cancelled | |
| 001833 | The Condition of this Mandate does not allow for payments | |
| 001834 | The user has disputed the payment | |
| 009999 | Technical error | |
| 001835 | The mandate has expired | No collection attempts were made confronting the mandate for over xiii months. As a result, information technology has expired, is inactive, and no further collections tin can be taken against it |
| 001836 | The mandate has been submitted to the user'southward banking company | The mandate has been submitted to the customer's bank to set up up against their bank account |
Live chat
No agent is free at the moment please ship us a request through our contact grade
sellerssheand.blogspot.com
Source: https://docs.mangopay.com/guide/errors
0 Response to "At t the Information Provided Is Not Valid Please Try Again"
Post a Comment