Reject a payment
If the Asynchronous Payment Statuses feature is not enabled, this
API operation sets the Gateway State field of the payment to FailedToSettle,
creates a refund for the payment amount, and returns the Refund object as response.
If the Asynchronous Payment Statuses feature is enabled, for ACH and Bank Transfer
payments, this API operation sets the Payment Status field to Error and the
Gateway State field to FailedToSettle, and unapply the payment if it is already
applied.
If the reason code “Payment Rejection” is active in the Reason Codes list, the reason code of the external refund is set to “Payment Rejection”. Otherwise, the default reason code in the list is used.
Authentication
Use Bearer {{token}} in the Authorization header for authentication.
Path parameters
The payment number starting with “P-” or the unique payment ID.
Headers
Include the Accept-Encoding: gzip header to compress responses as a gzipped file. It can significantly reduce the bandwidth required for a response.
If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a Content-Encoding header with the compression algorithm so that your client can decompress it.
Include the Content-Encoding: gzip header to compress a request. With this header specified, you should upload a gzipped file for the request payload instead of sending the JSON payload.
A custom identifier for tracing the API call. If you set a value for this header, Zuora returns the same value in the response headers. This header enables you to associate your system process identifiers with Zuora API calls, to assist with troubleshooting in the event of an issue.
The value of this field must use the US-ASCII character set and must not include any of the following characters: colon (:), semicolon (;), double quote ("), and quote (').
An entity ID. If you have Zuora Multi-entity enabled and the OAuth token is valid for more than one entity, you must use this header to specify which entity to perform the operation in. If the OAuth token is only valid for a single entity, or you do not have Zuora Multi-entity enabled, you should not set this header.
Comma separated IDs. If you have Zuora Multi-Org enabled, you can use this header to specify which orgs to perform the operation in. If you do not have Zuora Multi-Org enabled, you should not set this header.
The IDs must be a sub-set of the user’s accessible orgs. If you specify an org that the user does not have access to, the operation fails. This header is important in Multi-Org (MO) setups because it defines the organization context under which the API should operate—mainly used for read access or data visibility filtering. If the header is not set, the operation is performed in scope of the user’s accessible orgs.
The minor API version.
For a list of available minor versions, see API upgrades.
Request
The date and time of the transaction settlement. The format is yyyy-mm-dd hh:mm:ss.
Response headers
This header is returned if you specify the Accept-Encoding: gzip request header and the response contains over 1000 bytes of data.
Note that only the following MIME types support gzipped responses:
application/jsonapplication/xmltext/htmltext/csvtext/plain
The request limit quota for the time window closest to exhaustion. See rate limits for more information.
The number of requests remaining in the time window closest to quota exhaustion. See rate limits for more information.
The number of seconds until the quota resets for the time window closest to quota exhaustion. See rate limits for more information.
The type of the concurrency limit, which can be Default, High-volume transactions, or Object Query.
For more information, see Concurrent request limits.
The total number of the permitted concurrent requests.
For more information, see Concurrent request limits.
The remaining number of the permitted concurrent requests.
For more information, see Concurrent request limits.
Response
The date and time when the payment was cancelled, in yyyy-mm-dd hh:mm:ss format.
The date and time when the chargeback is created, in yyyy-mm-dd hh:mm:ss format. For example, 2019-03-01 15:31:10.
The message returned from the payment gateway for the payment. This message is gateway-dependent.
The code returned from the payment gateway for the payment. This code is gateway-dependent.
The status of the payment in the gateway; specifically used for reconciliation.
The date and time when a charge was marked and waiting for batch submission to the payment process, in yyyy-mm-dd hh:mm:ss format.
The unique identification number of the payment. For example, P-00000001.
The organization that this object belongs to.
Note: This field is available only when the Multi-Org feature is enabled.
The date when the refund takes effect, in yyyy-mm-dd format. For example, 2017-03-01.
The date and time when the refund was issued, in yyyy-mm-dd hh:mm:ss format.
The date and time when the transaction is settled, in yyyy-mm-dd hh:mm:ss format.
A payment gateway-specific field that maps Zuora to other gateways.
A payment gateway-specific field that maps Zuora to other gateways.
The date and time when the payment was submitted, in yyyy-mm-dd hh:mm:ss format.
Returns true if the request was processed successfully.
The date and time when the payment was last updated, in yyyy-mm-dd hh:mm:ss format. For example, 2019-03-02 15:36:10.