# Code and Formats source: https://developer.mastercard.com/payment-initiation-api/documentation/code-and-formats/index.md ## HTTP Response Codes {#http-response-codes} Resource requests use HTTP response codes to provide a coarse-grain indication of the result of each request. The most common expected response codes for the supported HTTP methods are as follows: | HTTP Response Code | Response Description | |----------------------------|---------------------------------------------------------------------------------------------------------------------------| | 200 (OK) | The request was completed successfully. | | 201 (CREATED) | Successful creation occurred using a POST request. The Location header will contain a link to the newly created resource. | | 204 (NO CONTENT) | Successful update occurred using a PUT request. | | 400 (BAD REQUEST) | General error when the request could not be fulfilled due to errors such as validation errors or missing required data. | | 401 (UNAUTHORIZED) | Missing or invalid authentication token. | | 403 (FORBIDDEN) | The user has insufficient permissions to a resource or action. | | 404 (NOT FOUND) | The requested resource was not found. | | 422 (UNPROCESSABLE ENTITY) | Resource already exists. or Resource has been modified. | ## Gateway Error Codes {#gateway-error-codes} Apart from the error codes returned by the Payment Initiation API, error codes can be returned by the Mastercard gateway, which verifies your request's signature and routes to the correct location. For further information about the 4xx response codes returned by the gateway and their possible resolutions, see [Gateway Error Codes](https://developer.mastercard.com/platform/documentation/security-and-authentication/gateway-error-codes/). ## Error Structure {#error-structure} To ensure a consistent experience across all Mastercard APIs, the following structure is followed by the Payment Initiation API for each error scenario that can occur. **Single Error:** ```json { "Errors": { "Error": [ { "source": "", "recoverable": "e.g. true/false", "details": "One of the request parameters is invalid, try again with the correct request." } ] } } ``` **Multiple Errors:** ```json { "Errors": { "Error": [ { "Source": "", "ReasonCode": "", "Description": "", "Recoverable": "true/false", "Details": "" },{ "source": "", "description": "", "recoverable": "true/false", "Details": "" } ] } } ``` | Field | Description | |-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Source** | The application that generated this error. Every error message that is generated and returned by the Gateway will have this field set to `Gateway`. If the field value is `PAYMENTINITIATION_API`, then the error is generated by the Payment Initiation application. | | **ReasonCode** | A unique constant identifies the error case encountered when any Payment Initiation API is called. For example, `FORBIDDEN` is used when the user has insufficient permissions to a resource or action. | | **Description** | Description of the `ReasonCode` field provided with additional details. | | **Recoverable** | Indicates whether this error will always be returned for this request, or retrying could change the outcome. For example, if the request contains an invalid request parameter, retrying will never result in success. However, if the error is related to some unexpected timeout with the service, retrying the call could result in a successful response. | | **Details** | Provide detailed error information wherever appropriate to help in resolving errors. | ## Payment Initiation Request Error Codes {#payment-initiation-request-error-codes} ### Payment Preference Request Error Codes {#payment-preference-request-error-codes} If you submit payment instructions that violate the supplier's payment preferences, you will receive the following warning or rejection message codes. Note: The warning messages do not affect the payment flow. If a warning message is received, the system still processes the payment. | Reason Code | Description | Tip to Resolve | |------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `CARD_WARNING` | `{supplierId}` flags all `{paymentMethod}` transactions. The transaction will be reviewed by the Supplier for acceptance and the status updated accordingly. | No immediate action is required. Monitor the transaction status while the supplier reviews the payment. | | `CARD_REJECTED` | Transaction rejected. `{paymentMethod}` is not accepted by this supplier. | The supplier does not accept this payment method. Use an alternate payment method or contact the [CTS Commercial Team](mailto:CTS.Commercial@mastercard.com) for guidance | | `NO_CUSTOMER_NUMBER_WARNING` | This transaction is in transit. Supplier ID flags payments, which do not include Customer Numbers for all invoices when making payments. | No action is required at this stage. The transaction will continue through processing and be reviewed by the supplier. | | `NO_CUSTOMER_NUMBER_REJECT` | Supplier ID requires that Customer Number is included for all invoices when making Payment Method payments. Resubmit with Customer Number included. | Review the request payload as per the API Reference. | | `CUSTOMER_NUMBER_WARNING` | This transaction is in transit. Supplier ID flags all Payment Method transactions from customer account number Customer Number. The transaction will be delivered to the Supplier for acceptance and the status updated accordingly. | No immediate action is required. The supplier will review the transaction and update the status accordingly. | | `CUSTOMER_NUMBER_REJECTED` | Transaction rejected. Payment Method transactions from customer account number Customer Number will not be accepted by this Supplier. | Use a different customer number or consult your Mastercard representative. | | `MAX_INSTRUCTED_AMT_WARNING` | This transaction is in transit. `{supplierId}` flags all `{paymentMethod}` transactions that exceed the maximum instructed amount allowed. The transaction will be reviewed by the Supplier for acceptance and the status updated accordingly. | No action is required at this stage. The supplier will review the transaction for acceptance. | | `MAX_INSTRUCTED_AMT_REJECTED` | Transaction rejected. The transaction amount exceeds the maximum instructed amount allowed through `{paymentMethod}` by this supplier. | Reduce the transaction amount or use an alternate payment method that supports the instructed amount. | | `MIN_INSTRUCTED_AMT_WARNING` | This transaction is in transit. `{supplierId}` flags all `{paymentMethod}` transactions less than the minimum-instructed amount allowed. The transaction will be reviewed by the supplier for acceptance and the status updated accordingly. | No action is required at this stage. The supplier will review the transaction for acceptance. | | `MIN_INSTRUCTED_AMT_REJECTED` | The transaction is rejected. The transaction amount is less than the minimum-instructed amount allowed through `{paymentMethod}` by this Supplier. | Increase the transaction amount to meet the minimum requirement or use an alternate payment method. | | `BUYER_ID_WARNING` | This transaction is in transit. `{supplierId}` flags all `{paymentMethod}` transactions from `{buyerId}`. The transaction will be reviewed by the supplier for acceptance and the status updated accordingly. | No immediate action is required. The transaction will be reviewed by the supplier. | | `BUYER_ID_REJECTED` | The transaction is rejected. `{paymentMethod}` transactions from `{buyerId}` are not accepted by this supplier. | Payments from this buyer ID are not accepted. Use a different buyer ID or consult your Mastercard representative. | | `FLAT_AMOUNT_WARNING` | This transaction is in transit. `{supplierId}` flags `{paymentMethod}` payments that do not include a `` charge. The transaction will be reviewed by the Supplier for acceptance and the status updated accordingly. | No action is required at this stage. The supplier will review the transaction for acceptance. | | `FLAT_AMOUNT_REJECTED` | Supplier `{supplierId}` requires that `{paymentMethod}` payments include a `` for acceptance. Resubmit with the `` charge. | Update the request to include the required flat fee amount, then resubmit the payment. | | `PERCENT_AMT_WARNING` | This transaction is in transit. `{supplierId}` flags `{paymentMethod}` payments that do not include a `` charge. The transaction will be reviewed by the supplier for acceptance and the status updated accordingly. | No immediate action is required. The supplier will review the transaction and update the status. | | `PERCENT_AMT_REJECTED` | Supplier `{supplierId}` requires that `{paymentMethod}` payments to include a `` for acceptance. Resubmit with the `` charge. | Update the request to include the required percentage-based fee, then resubmit the payment. | | `TIME_REJECTED` | This transaction was rejected. One or more invoices exceeds the number of days after the invoice date that a `{paymentMethod}` payment can be made. | Use a different payment method or submit a new payment within the allowed timeframe. | | `MAX_DAYS_AFTER_RELATED_DATE_REJECT` | Supplier `{supplierId}` requires that `{paymentMethod}` payments are made no later than `<# of Days After Invoice Date>` calendar days after the related date. Resubmit with another payment method. | The payment exceeds the supplier's allowed timeframe. Resubmit using a different payment method. | | `MAX_DAYS_AFTER_RELATED_DATE_WARNING` | This transaction is in transit. `{supplierId}` flags `{paymentMethod}` payments that are made later than `<# of Days After Invoice Date>` calendar days after the related date of the referred document for acceptance due to a payment control violation. The transaction will be delivered to the Supplier for acceptance and the status updated accordingly. | No immediate action is required. The transaction will be reviewed by the supplier. | | `FEE_PERCENT_DAYS_AFTER_INVOICE_REJECT` | Supplier `{supplierId}` requires that `{paymentMethod}` payments include a `` fee when made `<# of Days After Invoice Date>` calendar days after the invoice date. Resubmit with the `` fee. | Update the request to include the required percentage-based fee, then resubmit the payment. | | `FEE_PERCENT_DAYS_AFTER_INVOICE_WARNING` | This transaction is in transit. `{supplierId}` flags `{paymentMethod}` payments include a `` fee when sent `<# of Days After Invoice Date>` calendar days after the invoice date due to a payment preference violation. The transaction will be delivered to the Supplier for acceptance and the status updated accordingly. | No action is required at this stage. The supplier will review the transaction for acceptance. | | `FEE_FLAT_DAYS_AFTER_INVOICE_REJECT` | Supplier `{supplierId}` requires that `{paymentMethod}` payments include a `` fee when made `<# of Days After Invoice Date>` calendar days after the invoice date. Resubmit with the `` fee. | Update the request to include the required flat fee amount, then resubmit the payment. | | `FEE_FLAT_DAYS_AFTER_INVOICE_WARNING` | This transaction is in transit. `{supplierId}` flags `{paymentMethod}` payments include a `` fee when sent `<# of Days After Invoice Date>` calendar days after the invoice date due to a payment preference violation. The transaction will be delivered to the Supplier for acceptance and the status updated accordingly. | No immediate action is required. The transaction will be reviewed by the supplier. | | `NO_RELATED_DATE_REJECT` | Supplier `{supplierId}` requires that a related date is included for all invoices when making `{paymentMethod}` payments. Resubmit with related dates included. | Update the request to include the required related dates for all invoices, then resubmit the payment. | | `NO_RELATED_DATE_WARNING` | This transaction is in transit. Supplier `{supplierId}` flags payments, which do not include related dates for all invoices when making `{paymentMethod}` payments. | No action is required at this stage. The transaction will continue through supplier review. | ### Payment Rejected and Payment Declined Request Error Codes {#payment-rejected-and-payment-declined-request-error-codes} If the Creditor Agent updates the payment status to DECLINED or REJECTED, you will receive one of the following reason codes from the CDP. | Reason Code | Description | Tip to Resolve | |------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| | `SUPPLIER_SYSTEM_DOWN` | Unable to find an updated and accurate account number for the Supplier. | No immediate action is required. Retry the transaction once the supplier system becomes available or after account details are updated. | | `NO_PARTIAL_PAYMENT` | Supplier `{supplierId}` will not accept partial payments at this time. | Update the request to submit the full payment amount in a single transaction, then resubmit. | | `ALT_MOP` | Transaction `` has failed, `{buyerId}` needs to use an alternative method of payment for transacting to `{supplierId}`. | Resubmit the transaction using an alternate supported method of payment for this supplier. | | `ALT_MOP_NOT_BPS` | Transaction `` has failed, `{supplierId}` does not accept CDP payment from this `{buyerId}`. | Use a different payment method or submit the payment through a supported channel for this supplier. | | `UNSUPPORTED_CURRENCY_BY_SUPPLIER` | `` has failed, the supplier does not accept the selected currency. | Resubmit the transaction using a currency supported by the supplier. | | `INVOICE_NOT_SUPPORTED` | Transaction `` is rejected. The accepting Supplier Payment Agent does not support one or more invoices. | Review the invoice details and remove or correct unsupported invoices before resubmitting. | | `INVALID_INVOICE_DATA` | Transaction `` is rejected. One or more invoices include information that creates a reconciliation mismatch for the accepting Supplier Payment Agent. | Correct the invoice data to resolve reconciliation mismatches, then resubmit the transaction. | | `INVALID_CREDIT_NOTE_DATA` | Transaction `` is rejected. One or more credit notes include information that creates a reconciliation mismatch for the accepting Supplier Payment Agent. | Review and correct the credit note details in the request payload, then resubmit. | | `NO_CVV` | Card Verification Value is required. Please use a valid Card Verification Value numerical minimum length is 3 and maximum length is 4. | Provide a valid CVV (3--4 digits) in the request payload and resubmit the transaction. | ### Payment Cancellation Request Error Codes {#payment-cancellation-request-error-codes} When you submit a cancellation request, you may receive one or more of the following error codes either if the required data is missing or if the data you provided is incorrect. | Reason Code | Description | Tip to Resolve | |----------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| | `CANCELLED_BY_BUYER_AGENT` | Contact the Buyer for more information. | Contact the buyer directly to understand the reason for cancellation and determine next steps before initiating a new transaction. | | `BPA_REQUESTED` | Buyer Payment Agent (Debtor Agent) has requested to cancel the transaction. | Confirm that the transaction is in the SUBMITTED status and proceed with cancellation handling as applicable. | | `SPA_REQUESTED` | Supplier Payment Agent (Creditor Agent) has requested to cancel the transaction. | Monitor the transaction status and coordinate with the supplier to understand the cancellation reason before taking further action. | ### Payment Cancellation Rejected Error Codes {#payment-cancellation-rejected-error-codes} When the cancellation request is rejected, you may receive one or more of the following error codes either if the required data is missing or if the data you provided is incorrect. | Reason Code | Description | Tip to Resolve | |--------------------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------| | `CARD_DEBITED` | Transaction `{instructionIdentification}` cancellation rejected. The card was debited for the `{instructionIdentification}` already. | The payment has already been completed. Do not retry cancellation; reconcile the transaction and proceed with settlement handling. | | `PAYMENT_PROCESSED` | Transaction `{instructionIdentification}` cancellation rejected. `{paymentMethod}` payment was processed already. | The payment is already processed. Cancellation is no longer permitted; proceed with reconciliation or downstream handling. | | `CANNOT_HONOR_REQUEST` | Transaction `{instructionIdentification}` cancellation rejected. Supplier cannot honor the request. | Review supplier constraints and determine next steps, such as resubmitting a new transaction if applicable. | | `FAILED` | Transaction `{instructionIdentification}` has failed. | Verify that the `{requestedExecutionDate}` is today or a future date, then correct and resubmit the transaction. | | `NOT_PERMITTED` | Transaction `{instructionIdentification}` has failed, transaction not approved by the issuing Bank. | Verify that all card details are correct and that the card is authorized for this transaction type before retrying. | | `NO_REPLY` | Transaction `{instructionIdentification}` has failed, unable to reach issuing Bank. | Retry the transaction after a short interval or once connectivity with the issuing bank is restored. | | `PROCESSOR_DOWN` | Transaction `{instructionIdentification}` has failed, system down. | Retry the transaction once the processing system is available. No payload changes are required. | | `CAPTURE_CARD` | Transaction `{instructionIdentification}` has failed, capture card. | Do not retry the transaction with the same card. Use a different card or payment method. | | `DO_NOT_HONOR` | Transaction `{instructionIdentification}` has failed, do not honor. | Use an alternate card or payment method, or validate card eligibility before resubmitting. | | `INVALID_TRANSACTION` | Transaction `{instructionIdentification}` has failed, invalid transaction. | Ensure the `{requestedExecutionDate}` is today or in the future, then correct and resubmit the request. | | `SECURITY_VIOLATION` | Transaction `{instructionIdentification}` has failed, three-digit CVV2 or CVC or the four-digit CID security code was incorrect. | Enter the correct CVV/CVC/CID security code and resubmit the transaction. | | `DUPLICATE_TRANSMISSION` | Transaction `{instructionIdentification}` has failed, duplicate transmission detected. | Check transaction history to confirm duplication and avoid resubmitting the same request. | | `SPA_SYSTEM_ERROR` | Transaction `{instructionIdentification}` cancellation rejected. System error from supplier. | Retry the cancellation request after the supplier system issue is resolved. | ## Payment Initiation Response Error Codes {#payment-initiation-response-error-codes} | Reason Code | Description | Tip to Resolve | |---------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| | `AGENT_ID_INACTIVE` | The Agent ID is inactive | Your Agent ID is inactive. Contact the [CTS Commercial Team](mailto:CTS.Commercial@mastercard.com) to get approval. | | `AGENT_ID_REQUIRED` | The Agent ID is missing | Verify that the Agent ID is valid as per the API Reference, and based on the ID provided in the response update the Agent ID | | `BUYER_DETAILS_UNAVAILABLE` | The Buyer not found for the giver Buyer ID | Enter the Buyer details as per the API Reference, and based on the details provided in the response update the record | | `BUYER_DETAILS_UNAVAILABLE_FOR_GIVEN_ORG_ID` | The Buyer details are not available for the provided organization ID | Refer API Reference and enter the Buyer details as per the given organization ID. | | `BUYER_ID_NOT_ASSOCIATED` | The Buyer ID included in the request is not associated with the payment profile | Verify that the buyer ID is valid as per the API Reference, and based on the ID provided in the response update the buyer ID | | `BUYERID_NOT_EXIST` | The Buyer ID does not exist | Verify that the buyer ID is valid as per the API Reference, and based on the ID provided in the response update the buyer ID | | `CURRENCY_MISMATCH` | Currency mismatch between instructed amount and referred amount \[ {Type} \] \[ {Number} \] | Verify that the currency is valid as per API Reference, and based on the value provided in the response update the request parameters | | `EXPIRED_CARD` | The card is expired | Your card is expired. Contact the [CTS Commercial Team](mailto:CTS.Commercial@mastercard.com) to activate the card. | | `FAILED_MOD10_CHECK` | The provided PAN failed the Mod10 validation | Verify that the PAN is valid as per API Reference. Based on the value provided in the response, update the request parameters. | | `FAILED_TO_CREATE_BUYER` | Error while creating new buyer with given Org IDs | Refer to the API Reference and enter the Buyer details as per the given organization ID. | | `FAILED_TO_UPDATE_BUYER` | Error while updating buyer | Verify that the buyer data is valid as per API Reference, and based on the value provided in the response update the buyer detail. | | `INVALID_ACCOUNT_NUMBER` | The account number is invalid OR the account number either exceeds the maximum allowed length. | Verify that the account number is valid as per the API Reference. Based on the value provided in the response, update the mobile number and try again. | | `INVALID_ANYBIC_IDENTITY` | The anyBIC identification ID is invalid | Verify that the anyBIC identification ID is valid as per the API Reference, and based on the value provided in the response update the record. | | `INVALID_BPS_CODE` | The Track BPS code is invalid | Verify that the BPS code is valid as per the API Reference. Based on the value provided in the response, update the record. | | `INVALID_BUYER_DETAILS` | The Buyer details are invalid | Verify that the buyer detail is valid as per the API Reference, and based on the value provided in the response update the buyer details. | | `INVALID_BUYER_ID` | The Buyer ID {buyerId} is either not valid or not associated with your profile | Verify that the buyer ID is valid as per the API Reference, and based on the ID provided in the response update the buyer ID | | `INVALID_BUYER_ID_PATTERN` | The Buyer ID pattern is invalid | Verify that the buyer ID is valid as per the API Reference, and based on the ID provided in the response update the buyer ID | | `INVALID_BUYER_PROFILE_DETAILS` | The Buyer profile details are invalid | Verify that the buyer profile is valid as per the API Reference. Based on the ID provided in the response, update the buyer profile details. | | `INVALID_CARDHOLDER_NAME` | The cardholder name is invalid | Verify that the cardholder name is valid as per the API Reference. | | `INVALID_CREDITOR_IDENTIFICATION_CODE` | The creditor identification code is invalid | Verify that the creditor identification code is valid as per the API Reference. Based on the value provided in the response, update the record. | | `INVALID_DEBTOR_ACCOUNT_ID_SCHEMENAME_CODE` | The debtor account identification scheme name code is invalid. | Verify that the debtor identification code is valid as per the API Reference. Based on the value provided in the response, update the record. | | `INVALID_DEBTOR_ACCOUNT_IDENTIFICATION` | The debtor account identification is invalid | Verify that the debtor account ID is valid as per the API Reference. Based on the value provided in the response, update the record. | | `INVALID_DEBTOR_ACCOUNT_TYPE_CODE` | The debtor account type code is invalid. | Verify that the debtor account type is valid as per the API Reference. Based on the value provided in the response, update the record. | | `INVALID_DEBTOR_IDENTIFICATION_CODE` | The code in other identification field is invalid | Verify that the debtor identification code is valid as per the API Reference. Based on the value provided in the response, update the record. | | `INVALID_DEBTOR_NAME` | The debtor name is invalid | Verify that the debtor name is valid as per the API Reference. Based on the value provided in the response, update the record. | | `INVALID_EXPIRY_DATE` | The expiry date is invalid. | Verify the expiry date as per the API Reference, and try again. | | `INVALID_ICA_DETAILS` | The ICA details are invalid | Verify the ICA details as per the API Reference, and try again. | | `INVALID_INV_DATE` | The invoice date is invalid | Verify the invoice date as per the API Reference, and try again. | | `INVALID_LEI_IDENTITY` | The LEI identification ID is invalid | Verify that the LEI identification ID is valid as per the API Reference. Based on the value provided in the response, update the record, and try again. | | `INVALID_PAGE_LIMIT` | The page limit is invalid | Verify the page limit provided in the API Reference, and try again. | | `INVALID_PAGE_OFFSET` | The page offset is invalid | Verify the page offset provided in the API Reference, and try again. | | `INVALID_PAN` | The PAN is invalid | Verify that the PAN is valid as per the API Reference. Based on the value provided in the response, update the record, and try again. | | `INVALID_SCHEME_NAME_CODE` | The scheme name code is invalid | Verify the scheme name code as per the API Reference, and try again. | | `INVALID_SUPPLIER_DETAILS` | The supplier details are invalid | Verify that the supplier detail is valid as per the API Reference, and try again. | | `INVALID_SUPPLIER_EMAIL` | The Supplier email is invalid | Verify that the email is valid as per the API Reference. Based on the value provided in the response, update the record, and try again. | | `INVALID_SUPPLIER_ID_PATTERN` | The Supplier ID pattern is invalid | Verify that the supplier ID is valid as per the API Reference. Based on the ID provided in the response, update the supplier ID, and try again. | | `INVALID_SUPPLIER_PROFILE_DETAILS` | The Supplier profile details are invalid | Verify that the supplier profile detail is valid as per the API Reference, and try again. | | `INVALID_UNSTRUCTURED_DATA` | The unstructured data is invalid | Verify that the unstructured data is valid as per the API Reference, and try again. | | `MULTIPLE_BUYER_DETAILS` | More than one buyer found for given org details | Verify and match the buyer details as per the API Reference, and try again. | | `NO_CARD_CURRENCY` | The card information currency is missing. | Provide the required card currency field as defined in the API Reference, then resubmit the request. | | `NO_AMT` | The payment amount is missing | Verify that the request amount is valid as per API Reference, and based on the description provided in the response, update the request parameters. | | `NO_INSTRUCTED_AMT` | The payment amount is missing. | Enter the field input as per the API Reference. | | `NO_ADJ_AMT` | The adjustment amount is missing. The adjustment amount is required when invoice total and payment amount is not the same. | Enter the field input as per the API reference. | | `NO_DOCUMENT_TYPE` | The document type is missing. | Enter the field input as per the API reference. | | `NO_BREF_NUMBER` | The referred document information BREF number is missing. | Enter the field input as per the API reference. | | `INVALID_REMITTED_AMT` | The remitted amount is invalid, referred document \[ {Number} \] remitted amount reconciliation error. | Refer the API reference for correction of the error. | | `NO_INV_AMT` | The invoice amount is missing. | Enter the field input as per the API reference. | | `NO_INV_NUMBER` | The invoice number is missing. | Enter the field input as per the API reference. | | `NO_CLAM_NUMBER` | The referred document information CLAM number is missing. | Enter the field input as per the API reference. | | `NO_ADJUSTMENT_AMOUNT_CURRENCY` | The adjusted amount of currency is missing. | Enter the field input as per the API reference. | | `NO_RELATED_DATE` | The related date is missing. | Enter the field input as per the API reference. | | `NO_RELATED_DATE_TYPE` | The related date type code is missing. | Enter the field input as per the API reference. | | `NO_RELATED_REMITTANCE_METHOD` | The related remittance method is missing. | Enter the field input as per the API reference. | | `NO_REMITTANCE_INFORMATION` | The remittance information is missing. | Enter the field input as per the API reference. | | `NO_AMOUNT_TYPE` | The payment amount type code in the document is missing. | Enter the field input as per the API reference. | | `NO_CARD_DATA` | The card data is missing | Include all mandatory card data fields in the request payload as specified in the API Reference. | | `NO_CARDHOLDER_NAME` | The cardholder name is missing | Populate the cardholder name field in the request payload and resubmit. | | `NO_CHARGE_INFORMATION_CURRENCY` | The charge currency is missing | Add the required charge currency field to the request payload as per the API Reference. | | `NO_CREDIT_REFERENCE_TYPE` | The credit reference type code is missing. | Include a valid credit reference type code in the request payload. | | `NO_CREDIT_TRANSFER_TRANSACTION_INFORMATION` | The credit transfer transaction is missing. | Add the required credit transfer transaction section to the request payload. | | `NO_CREDIT_TRANSFER_TRANSACTION_INFORMATION_DETAILS` | The credit transfer transaction information details are missing. | Populate the missing credit transfer transaction details as defined in the API Reference. | | `NO_CREDITOR_IDENTIFICATION` | The creditor identification is missing | Provide the required creditor identification details in the request payload. | | `NO_CREDITOR_OTHER_IDENTIFICATION` | The creditor identification in other creditor field is missing | Populate the other creditor identification field with valid data and resubmit. | | `NO_CREDITOR_OTHER_IDENTIFICATION_CODE` | The identification code in other identification field is missing or incorrect | Provide a valid identification code in the other identification field as per the API Reference. | | `NO_CURRENCY` | The currency is missing | Specify a valid currency value in the request payload. | | `NO_DEBTOR_ACCOUNT_DETAILS` | The debtor account details are missing. | Include the required debtor account details in the request payload. | | `NO_DEBTOR_ACCOUNT_ID_SCHEMENAME_CODE` | The debtor account identification scheme name code is missing. | Provide the debtor account identification scheme name code as defined in the API Reference. | | `NO_DEBTOR_ACCOUNT_IDENTIFICATION` | The debtor account identification is missing. | Populate the debtor account identification field with valid data. | | `NO_DEBTOR_ACCOUNT_TYPE_CODE` | The debtor account type code is missing. | Add the required debtor account type code to the request payload. | | `NO_DEBTOR_ADDRESS` | The debtor postal address details are missing. | Include the debtor postal address details in the request payload. | | `NO_DEBTOR_DETAILS` | The debtor details are missing. | Populate all mandatory debtor details in the request payload. | | `NO_DEBTOR_IDENTIFICATION` | The debtor identification is missing. | Provide valid debtor identification details as specified in the API Reference. | | `NO_DEBTOR_NAME` | The debtor name is missing. | Add the debtor name field to the request payload and resubmit. | | `NO_DEBTOR_OTHER_IDENTIFICATION` | The debtor identification ID in other identification field is missing. | Populate the other debtor identification field with valid data. | | `NO_DECLINE_REASON` | The transaction status is DECLINED. | Include the required decline reason field in the request payload where applicable. | | `NO_EXPIRY_DATE` | The expiry date is missing. | Provide the card expiry date in the correct format and resubmit the request. | | `NO_MOP` | The method of payment is missing. | Specify a valid method of payment in the request payload. | | `NO_NOC` | The name on the card is missing. | Populate the name-on-card field in the request payload. | | `NO_OTHER_DEBTOR_IDENTIFICATION_CODE` | The code in the identification field is missing. | Provide a valid identification code in the debtor identification field. | | `NO_PAN` | The PAN is missing | Provide a valid PAN in the request payload and resubmit. | | `NO_PAY_INFO` | The payment information is missing. | Add the required payment information section to the request payload. | | `NO_PAYMENT_INFORMAT` | The payment information is missing. | Populate the payment information details as defined in the API Reference. | | `NO_PAYMENT_INFORMATION_IDENTIFICATION` | The payment information identification is missing. | Include a valid payment information identification value in the request payload. | | `NO_REQUESTED_EXECUTION_DATE` | The requested execution date is missing. | Specify the requested execution date and ensure it follows the supported date format. | | `NO_SUPPLEMENTARY_DATA` | The card details in supplementary data are missing. | Add the required card details under supplementary data in the request payload. | | `NO_TRANSACTION_ID` | The `instructionIdentification` is missing. | Provide a valid instruction identification value and resubmit the request. | | `NO_VALID_FROM_DATE` | The valid from date in additional card details is missing. | Populate the valid-from date in the additional card details section. | | `NO_VALID_TO_DATE` | The valid to date in additional card details is missing. | Populate the valid-to date in the additional card details section. | | `NON_UNIQUE_BUYER_DETAILS` | The unique Buyer not found for given org ID. | Verify the buyer details and organization ID, then update the request with a valid unique buyer. | | `REQUESTED_EXECUTION_DATE_OUT_OF_RANGE` | The requested execution date is invalid. | Verify that the requested execution date is valid as per the API Reference, and try again. | | `RETRIEVE_TRANSACTION` | Retrieve the transaction details from Track BPS before approving or declining this transaction | Contact the [CTS Commercial Team](mailto:CTS.Commercial@mastercard.com) to get the transaction detail. | | `SUPPLIERID_NOT_EXIST` | The Supplier ID does not exist | Enter the supplier ID as per the API Reference. Based on the ID provided in the response, update the supplier ID, and try again. | | `SUPPLIERID_PMT_INITIATION_DEACTIVATED` | The `{SupplierBpsId}` has been deactivated | Your Supplier BPS ID is inactive, contact the [CTS Commercial Team](mailto:CTS.Commercial@mastercard.com) to get approval. | | `INVALID_ADDITIONAL_REMITTANCE_INFORMATION` | The additional remittance information is invalid. | Correct the additional remittance information to match the supported format and values defined in the API Reference, then resubmit. | | `INVALID_ADJ_CODE` | The Adjustment code is invalid. | Update the adjustment code to a valid value from the supported list and resubmit the request. | | `INVALID_AMOUNT_TYPE` | The payment amount type code in the referred document is invalid. | Provide a valid payment amount type code as defined in the API Reference. | | `INVALID_AMT_MIN` | The invoice amount is invalid. | Correct the invoice amount to meet the supported format and value constraints, then resubmit. | | `INVALID_CREDIT_REFERENCE_TYPE` | The credit reference type code is invalid. | Update the credit reference type code to a valid value as defined in the API Reference. | | `INVALID_DOCUMENT_TYPE` | The document type is invalid, the value provided in referred document does not match the valid value list. | Replace the document type with a valid value from the supported document type list and resubmit. | | `INVALID_DOCUMENT_TYPE_ATTACHED` | The attached document type is invalid. | Attach a document using a supported document type as defined in the API Reference. | | `INVALID_LINE_DETAIL_ID` | The line item identification is invalid. | Correct the line item identification value to meet the required format and constraints. | | `INVALID_PAY_AMOUNT_VALUE` | The amount value specified in the instructed amount is invalid. | Update the instructed amount value to a valid numeric format and resubmit the request. | | `INVALID_PAY_AMT` | The transaction amount is invalid. | Correct the transaction amount to meet supported format and validation rules, then resubmit. | | `INVALID_PAYMENT_DUE_DATE` | The payment due date is invalid. | Provide a valid payment due date in the supported date format. | | `INVALID_RELATED_DATE_TYPE` | The related date type code is invalid. | Update the related date type code to a valid supported value. | | `INVALID_RELATED_REMITTANCE_METHOD` | The related remittance method is invalid. | Specify a valid remittance method as defined in the API Reference. | | `INVALID_REMITTANCE_INFORMATION` | The remittance information is invalid. | Correct the remittance information to align with supported structure and values, then resubmit. | | `DEBTOR_PROFILE_ID_EXISTS` | Enter a different Debtor Profile ID, Debtor Profile ID already exists. | Use a unique Debtor Profile ID that is not already assigned to another Debtor. | | `INVALID_DEBTOR_PROFILE_ID_FORMAT` `NO_DEBTOR_PROFILE_ID` | Enter Debtor Profile ID in the format `@`. | Ensure that the ID follows the correct pattern: `@`. | | `INVALID_LEGAL_BUSINESS_NAME` `INVALID_DBA_NAME` `NO_LEGAL_BUSINESS_NAME` | Enter a Name with 240 characters or less. | Review the field value and correct it according to the specification. | | `INVALID_LEGAL_ADDRESS_LINE` `INVALID_BILL_TO_ADDRESS_LINE` | Enter Address Line with 140 characters or less. | Add or correct the legal address line within the required length. | | `INVALID_LEGAL_ADDRESS_TOWN_NAME` `INVALID_BILL_TO_ADDRESS_TOWN_NAME` | Enter a Town Name with 140 characters or less. | Add or correct the Town Name within the required length. | | `INVALID_LEGAL_ADDRESS_COUNTRY_SUBDIVISION` | Enter a Country SubDivision with 35 characters or less. | Review the field value and correct it according to the specification. | | `INVALID_LEGAL_ADDRESS_POSTCODE` `INVALID_BILL_TO_ADDRESS_POSTCODE` | **NAM** US: Enter a valid Post Code with 5 to 10 digits. Spaces or hyphens are allowed. Canada: Enter a valid Post Code with 5 to 8 characters. Spaces or hyphens are allowed. **EUR** UK: Enter a valid Post Code with 6 to 8 characters. Spaces or hyphens are allowed. **LAC** Curacao(optional): Enter a valid Post Code up with 10 characters or less. Spaces or hyphens are allowed. Colombia: Enter a valid Post Code with 7 digits. Spaces or hyphens are allowed. Brazil: Enter a valid Post Code with 5 to 10 digits. Spaces or hyphens are allowed. **Other** All other countries: (optional): Enter a valid Post Code with 10 characters or less. Spaces or hyphens are allowed. | Enter a valid postcode per regional format. | | `INVALID_LEGAL_ADDRESS_COUNTRY` `INVALID_BILL_TO_ADDRESS_COUNTRY` | Enter country code in two-letter code format. | Enter a valid two‑letter country code. | | `INVALID_ORGANISATION_ID_TYPE` | Enter a valid Organisation Identification Type. | Review the field value and correct it according to the specification. | | `NO_LEGAL_ADDRESS` | Address is required. | Enter a valid Legal Address. | | `NO_TAX_ID` | Enter a Tax ID for an Organisation. | Review the field value and correct it according to the specification. | | `PAYMENT_PROFILE_LIMIT_EXCEEDED` | Remove one or more profiles. The total number of profiles associated with a Debtor cannot exceed 20. | Review the field value and correct it according to the specification. | | `NO_PAYMENT_METHOD` | Enter one or more payment methods supported by the Debtor and agent. Valid value is CARD. | Review the field value and correct it according to the specification. | | `BUSINESS_EXISTS` | This business already exists for this agent. | Update existing profile or register with a different identifier. | | `INVALID_PAYMENT_METHOD` | Enter one or more valid payment methods supported by the Debtor/Creditor and agent. Valid value is CARD. | Enter valid payment method. | | `INVALID_INACTIVE_REASON` | Enter a valid inactive reason. Valid values are PRE_REGISTERED and AGENT_HOLD. | Review the field value and correct it according to the specification. | | `NO_INACTIVE_REASON` | Enter an inactive reason. Valid values are PRE_REGISTERED or AGENT_HOLD. | Enter a valid reason and resubmit the request. | | `INVALID_TAX_ID` | **NAM** US: Enter a valid Tax ID with 9 digits. Canada: Enter a valid Tax ID with 9 digits. **EUR** UK: Enter a valid Tax ID with 10 digits. **LAC** Curacao: Enter a valid Tax ID with 9 digits. Colombia: Enter a valid Tax ID with 9 or 10 digits. Brazil: Enter a valid Tax ID with 14 digits. **Other** All other countries: (optional): Enter a valid Tax ID with 15 digits. | Enter a valid TAX ID per country‑specific format. | | `NO_LEGAL_ADDRESS_LINE` `NO_BILL_TO_ADDRESS_LINE` | Enter Address Line with 140 characters or less. | Enter a valid Address Line as per the specified limit. | | `NO_LEGAL_ADDRESS_TOWN_NAME` | Enter a Town Name with 140 characters or less. | Enter Town Name as per specified limit. | | `NO_LEGAL_ADDRESS_COUNTRY_SUBDIVISION` | Enter a Country SubDivision with 35 characters or less. | Enter a valid Country SubDivision as per the specified limit. | | `NO_LEGAL_ADDRESS_POSTCODE` | **NAM** US: Enter a valid Post Code with 5 to 10 digits. Spaces or hyphens are allowed. Canada: Enter a valid Post Code with 5 to 8 characters. Spaces or hyphens are allowed. **EUR** UK: Enter a valid Post Code with 6 to 8 characters. Spaces or hyphens are allowed. **LAC** Curacao(optional): Enter a valid Post Code up with 10 characters or less. Spaces or hyphens are allowed. Colombia: Enter a valid Post Code with 7 digits. Spaces or hyphens are allowed. Brazil: Enter a valid Post Code with 5 to 10 digits. Spaces or hyphens are allowed. **Other** All other countries: (optional): Enter a valid Post Code with 10 characters or less. Spaces or hyphens are allowed. | Enter a valid postcode per regional format. | | `NO_LEGAL_ADDRESS_COUNTRY` | Enter country code in two-letter code format. | Enter a two‑letter country code. | | `LEGAL_ADDRESS_SANCTIONED_COUNTRY` `BILL_TO_ADDRESS_SANCTIONED_COUNTRY` | Enter a different country. The country used in the request is sanctioned and cannot be used. | Select a non‑sanctioned country per compliance guidelines. | | `INVALID_PROFILE_STATE` | Enter a valid value for `is_active` flag for payment profile. Payment profile cannot be active when Debtor is inactive. | Ensure that the payment profile is not set to active when the Debtor is inactive. | | `DUPLICATE_EMAIL` | Enter a different email address. This email address is already in use with a different payment profile. | Verify that the email address is unique. | | `DUPLICATE_ORGANISATION_IDENTIFICATION_TYPE` | More than one Identification provided for the same Organisation Type. | Verify that each organisation has a unique identification type. | | `INVALID_BANK` | Enter a valid Bank Party Identification with 15 characters or less. | Re‑enter the corrected value and retry the operation. | | `INVALID_DUNS` | Enter a valid Data Universal Numbering System with 15 characters or less. | Enter a valid DUNS number as per the specified limit. | | `INVALID_CBID` | Enter a valid Central Bank Identification with 15 characters or less. | Enter a valid Central Bank Identification as per the specified limit. | | `INVALID_COID` | Enter a valid Country Identification Code with 15 characters or less. | Enter a valid Country Identification Code as per the specified limit. | | `INVALID_COID_UPDATE` | The Country Identification Code cannot be updated. A Country Identification Code already exists for this Debtor. | If the COID is incorrect, contact the [CTS Commercial Team](mailto:CTS.Commercial@mastercard.com) for review or corrective action. | | `INVALID_COUNTRY_UPDATE` | A Legal Address Country exists for this Debtor. The Legal Address Country cannot be updated. | Verify and retry with the input for Legal Address Country. | | `INVALID_CUST` | Enter a valid Customer Number with 15 characters or less. | Enter a valid Customer Number as per the specified limit. | | `INVALID_ORGANISATION_IDENTIFICATION` | Enter one or more valid Organisation Identification with 15 characters or less. | Enter one or more valid Organisation Identification as per the specified limit. | | `NO_ORGANISATION_IDENTIFICATION` | Enter one or more valid Organisation Identifications. | Enter at least one valid Organisation Identification value. | | `UNIDENTIFIED_FIELD` | `` is unidentified field. Check the request schema. | Correct the field name, resubmit the request. | | `INVALID_TAX_ID_UPDATE` | The Tax ID cannot be updated. A Tax ID already exists for this Debtor. | Verify and enter a valid Tax ID for an Organisation. | | `INVALID_REGISTRATION_ID` | Enter a valid Debtor registration ID. `` is either not valid or is not associated to your profile. | Verify and enter a valid Debtor registration ID. | | `INVALID_LIMIT` | Set the limit to 100 records or less for this request. You can only retrieve 100 records at a time. | Reduce record count to 100 or fewer per request. | | `DEBTOR_PROFILE_ID_NOT_FOUND` | Enter a valid Debtor Profile ID. Debtor Profile ID was not found. | Verify that the Debtor Profile ID exists and is correctly created in the system. | | `INVALID_BILL_TO_ADDRESS_COUNTRY_SUBDIVISION` | Enter a Country SubDivision with 35 characters or less. | Review the field value and correct it according to the specification. | | `NO_BILL_TO_ADDRESS_TOWN_NAME` | Enter a Town Name with 140 characters or less. | Enter Town Name as per the specified limit. | | `NO_BILL_TO_ADDRESS_COUNTRY_SUBDIVISION` | Enter a Country SubDivision with 35 characters or less. | Enter a valid Country SubDivision as per the specified limit. | | `NO_BILL_TO_ADDRESS_POSTCODE` | **NAM** US: Enter a valid Post Code with 5 to 10 digits. Spaces or hyphens are allowed. Canada: Enter a valid Post Code with 5 to 8 characters. Spaces or hyphens are allowed. **EUR** UK: Enter a valid Post Code with 6 to 8 characters. Spaces or hyphens are allowed. **LAC** Curacao(optional): Enter a valid Post Code up with 10 characters or less. Spaces or hyphens are allowed. Colombia: Enter a valid Post Code with 7 digits. Spaces or hyphens are allowed. Brazil: Enter a valid Post Code with 5 to 10 digits. Spaces or hyphens are allowed. **Other** All other countries: (optional): Enter a valid Post Code with 10 characters or less. Spaces or hyphens are allowed. | Enter a valid postcode per regional format. | | `NO_BILL_TO_ADDRESS_COUNTRY` | Enter country code in two-letter code format. | Enter a valid country code. | | `INVALID_PROFILE_STATE_UPDATE` | Enter a valid value for `is_active` flag. Debtor cannot be inactive when payment profile is active. | Ensure that the payment profile is not set to active when the Debtor is inactive. | | `INVALID_EMAIL` | Enter a valid email address. Ensure the format includes \[username\]@\[domain\].\[top level domain\]. | Verify that the email address is valid. | | `NO_PAYMENT_PROFILE` | Payment Profile is required. Please provide at least one Payment Profile. | Enter at least one valid Payment Profile. | | `INVALID_DELETE_PROFILE_REQUEST` | Mastercard CDP cannot process the delete profile request. Each active Debtor or Creditor must have at least one payment profile. | Ensure the Debtor or Creditor has at least one active payment profile before attempting to delete. | | `CREDITOR_PROFILE_ID_NOT_FOUND` | Creditor Profile is not found. | Verify and enter a valid Creditor Profile ID. | | `API_DOWN` | This CDP API is down. Try again later. | Check API environment status and retry. |