# HTTP Response Codes source: https://developer.mastercard.com/mastercard-send-disbursements/documentation/response-error-codes/http-response-reason-codes/index.md Successfully processed Disbursement API requests will result in response messages with HTTP code 201 (CREATED). A transaction response with an 'APPROVED' status (`"status": "APPROVED"`) indicates that the transaction was successful. In some situations, a transaction response can have an ['UNKNOWN' status](https://developer.mastercard.com/mastercard-send-disbursements/documentation/response-error-codes/status/index.md#unknown-or-pending-status). If the transaction is declined, the API response is either: * 201 response with `status` value as 'DECLINED', if the API request `decline_details` query parameter was set to 'true' * 402 error with `ReasonCode` as 'DECLINE' (the default) The tables below show the response codes that the application may return for Disbursement API requests. In the event of network or infrastructure issues, other response codes may be returned. **NOTE:** For further information about 4xx/5xx response codes and possible resolutions, see [Gateway Error Codes](https://developer.mastercard.com/platform/documentation/errors-and-troubleshooting/oauth1-and-mtls-error-codes/). The error response message parameters are described in [Error Codes](https://developer.mastercard.com/mastercard-send-disbursements/documentation/response-error-codes/error-codes/index.md). ## POST Responses {#post-responses} | HTTP code - Status | Outcome / Possible situation | Recommended action | |--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 201 Created - APPROVED | Transaction approved. The `funds_availability` field indicates when the Receiving Institution (RI) may post funds to the receiving account (such as immediate, same day, next calendar day). | Inform consumer of success. | | 201 Created - DECLINED | *(The decline response when `decline_details` set to 'true' in the POST request.)* Transaction declined, possibly due to the card account, partner limits, or an issue or delay between Mastercard and the RI. | Depending on the `merchant_advice_code` or `network_decision_code` in the response, you may be able to try a new request, see [Retrying a Declined Transaction](https://developer.mastercard.com/mastercard-send-disbursements/documentation/tutorials-and-guides/declined-txn/index.md). | | 201 Created - PENDING | *(Possible response for a Repeat Flag POST request.)* Request accepted and Payment Transaction sent to the RI. Awaiting status. | See [Procedure When Transaction Status 'UNKNOWN' or 'PENDING'](https://developer.mastercard.com/mastercard-send-disbursements/documentation/tutorials-and-guides/exception-management/index.md#procedure-when-transaction-status-unknown-or-pending). | | 202 Accepted - UNKNOWN | Request accepted but transaction status not yet known. Possible communication delay between Mastercard and the RI. Processing of the request will continue asynchronously. | See [Procedure When Transaction Status 'UNKNOWN' or 'PENDING'](https://developer.mastercard.com/mastercard-send-disbursements/documentation/tutorials-and-guides/exception-management/index.md#procedure-when-transaction-status-unknown-or-pending). | | 400 Bad Request, 401 Unauthorized, 403 Forbidden | Issue with the API request, such as missing required field, invalid value, incorrect authentication, partner not onboarded. | See [Error Codes](https://developer.mastercard.com/mastercard-send-disbursements/documentation/response-error-codes/error-codes/index.md). | | 402 Error - DECLINE | *(The default decline response when `decline_details` not used in the POST request.)* Transaction declined. Could be due to the card account, partner limits, or an issue or delay between Mastercard and the RI. The `Description` field indicates the reason (such as card declined, card expired, partner has exceeded daily limit) | Can use a GET call to retrieve more details. In that response, `merchant_advice_code` or `network_decision_code` will be present, indicating whether you can try a new request, see [Retrying a Declined Transaction](https://developer.mastercard.com/mastercard-send-disbursements/documentation/tutorials-and-guides/declined-txn/index.md). | | 408 Request Timeout (no response) | Timeout while waiting for the response. Request may or may not have reached Mastercard systems and been processed, or there may be an issue sending a response to the client. | See [Procedure When Timeout or Server Error Response](https://developer.mastercard.com/mastercard-send-disbursements/documentation/tutorials-and-guides/exception-management/index.md#procedure-when-timeout-or-server-error-response). | | 409 Conflict | Duplicate Disbursement Reference ID detected for what seems to be a unique transaction request; the POST request did not meet [Repeat Flag or Idempotency requirements](https://developer.mastercard.com/mastercard-send-disbursements/documentation/tutorials-and-guides/repeat-flag/index.md). | Use a unique Disbursement Reference ID for each new transaction request. | | 429 Too Many Requests | You have sent too many requests in a given amount of time ('rate limiting'). For the API rate limits, see [this page](https://developer.mastercard.com/mastercard-send-disbursements/documentation/support/index.md). This is a courtesy response. When the service is receiving a very large number of requests from a single party, the system may just drop connections to minimize resource monopolization. | Use retry logic with exponential back‑off to resend the transaction request. | | 5XX Internal Server Error | Server-side error during processing. Transaction status is unclear. Could be an issue/delay between Mastercard and RI. | See [Procedure When Timeout or Server Error Response](https://developer.mastercard.com/mastercard-send-disbursements/documentation/tutorials-and-guides/exception-management/index.md#procedure-when-timeout-or-server-error-response). | | 5XX Server Error | Request may not have reached Mastercard systems. Typically indicates an error in the network infrastructure between the client and Mastercard Send API server. Such errors will never contain the Mastercard Send API error structure in the response. | See [Procedure When Timeout or Server Error Response](https://developer.mastercard.com/mastercard-send-disbursements/documentation/tutorials-and-guides/exception-management/index.md#procedure-when-timeout-or-server-error-response). | | 502 Transaction Not Processed | The transaction request likely did not reach Mastercard Send. | See [Procedure When Timeout or Server Error Response](https://developer.mastercard.com/mastercard-send-disbursements/documentation/tutorials-and-guides/exception-management/index.md#procedure-when-timeout-or-server-error-response). | | Bad format response | Rare situation, likely caused by a system glitch. The response is improperly formatted and does not have the typical response fields or error fields. | See [Procedure When Bad Format Response](https://developer.mastercard.com/mastercard-send-disbursements/documentation/tutorials-and-guides/exception-management/index.md#procedure-when-bad-format-response). | ## GET-Specific Responses {#get-specific-responses} In addition to the following responses, you may receive some of the responses shown in the table above. | HTTP code - Status | Outcome / Possible situation | Recommended action | |--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 200 OK - APPROVED | Transaction approved. The `funds_availability` field indicates when the RI may post funds to the receiving account (such as immediate, same day, next calendar day). | Inform consumer of success. | | 200 OK - DECLINED | Transaction declined, possibly due to the card account, partner limits, or an issue or delay between Mastercard and the RI. | Depending on the `merchant_advice_code` or `network_decision_code` in the response, you may be able to try a new request, see [Retrying a Declined Transaction](https://developer.mastercard.com/mastercard-send-disbursements/documentation/tutorials-and-guides/declined-txn/index.md). | | 200 OK - UNKNOWN or PENDING | Transaction status not yet known. Possible communication delay between Mastercard and the RI. Processing of the request will continue asynchronously. | See [Procedure When Transaction Status 'UNKNOWN' or 'PENDING'](https://developer.mastercard.com/mastercard-send-disbursements/documentation/tutorials-and-guides/exception-management/index.md#procedure-when-transaction-status-unknown-or-pending). | | 200 OK - ERROR | There were errors in the transaction request, or a network or system error prevented processing of the transaction. | You can try the transaction request again as a new transaction POST request with a unique Disbursement Reference ID (not a Repeat Flag POST request). | | 200 OK - REVERSED or CANCELLED | The transaction request has been subsequently reversed or cancelled. Approved Mastercard Send Payment Transactions are generally irrevocable and can only be reversed in exceptional circumstances. | --- | | 404 Not Found | A transaction request with the supplied Disbursement Reference ID or Disbursement ID was not found. | Check the ID. If you are trying to retrieve a transaction requested within the past 24 hours, wait 60 seconds, then resend the GET request. If you get another 404 response, you can retry the transaction request as a [Repeat Flag POST request](https://developer.mastercard.com/mastercard-send-disbursements/documentation/tutorials-and-guides/repeat-flag/index.md). |