Refund a credit memo
Note: This operation is only available if you have Invoice Settlement enabled. The Invoice Settlement feature is generally available as of Zuora Billing Release 296 (March 2021). This feature includes Unapplied Payments, Credit and Debit Memo, and Invoice Item Settlement. If you want to enable Invoice Settlement, see Invoice Settlement Enablement and Checklist Guide for more information.
Refunds a full or partial posted credit memo to your customers. Only the amount of unapplied part could be refunded.
You can refund a credit memo only if you have the user permission. See Billing Roles for more information.
When you refund a credit memo, the total number of credit memo items to be refunded must be less than or equal to 15,000.
For a use case of this operation, see Refund processing.
Authentication
Use Bearer {{token}} in the Authorization header for authentication.
Path parameters
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
It contains Home currency and Reporting currency custom rates currencies. The maximum number of items is 2 (you can pass the Home currency item, Reporting currency item, or both).
Note:
- This field is available only if you are on the latest Zuora API version, or you set the
Zuora-Versionrequest header to224.0or a later version. - You cannot set the custom rates, if both the Automatically include additional Currency Conversion information in data source exports option and Fx data feature are enabled.
The field used to pass gateway-specific parameters and parameter values.
Container for credit memo items. The maximum number of items is 1,000.
Note: This field is only available if you have the Invoice Item Settlement feature enabled. Invoice Item Settlement must be used together with other Invoice Settlement features (Unapplied Payments, and Credit and Debit memos). If you wish to enable Invoice Settlement, see Invoice Settlement Enablement and Checklist Guide for more information.
The date when the refund takes effect, in yyyy-mm-dd format. The date of the refund cannot be before the credit memo date. Specify this field only for external refunds. Zuora automatically generates this field for electronic refunds.
A payment gateway-specific field that maps to Zuora for the gateways, Orbital, Vantiv and Verifi.
A payment gateway-specific field that maps to Zuora for the gateways, Orbital, Vantiv and Verifi.
ID of the corresponding object in NetSuite. Only available if you have installed the Zuora Connector for NetSuite.
Status of the refund’s synchronization with NetSuite. Only available if you have installed the Zuora Connector for NetSuite.
Origin of the corresponding object in NetSuite. Only available if you have installed the Zuora Connector for NetSuite.
Date when the refund was synchronized with NetSuite. Only available if you have installed the Zuora Connector for NetSuite.
Specifies whether the refund should be synchronized with NetSuite. Only available if you have installed the Zuora Connector for NetSuite.
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 refund was cancelled, in yyyy-mm-dd hh:mm:ss format.
The date and time when the refund was created, in yyyy-mm-dd hh:mm:ss format. For example, 2017-03-06 15:31:10.
The message returned from the payment gateway for the refund. This message is gateway-dependent.
The response code returned from the payment gateway for the refund. This code is gateway-dependent.
The date and time when a refund was marked and waiting for batch submission to the payment process, in yyyy-mm-dd hh:mm:ss format.
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.
The date and time when the refund was issued, in yyyy-mm-dd hh:mm:ss format.
The date and time when the refund was settled in the payment processor, in yyyy-mm-dd hh:mm:ss format. This field is used by the Spectrum gateway only and not applicable to other gateways.
A payment gateway-specific field that maps to Zuora for the gateways, Orbital, Vantiv and Verifi.
A payment gateway-specific field that maps to Zuora for the gateways, Orbital, Vantiv and Verifi.
The date and time when the refund was submitted, in yyyy-mm-dd hh:mm:ss format.
Returns true if the request was processed successfully.
The date and time when the refund was last updated, in yyyy-mm-dd hh:mm:ss format. For example, 2017-03-07 15:36:10.
ID of the corresponding object in NetSuite. Only available if you have installed the Zuora Connector for NetSuite.
Status of the refund’s synchronization with NetSuite. Only available if you have installed the Zuora Connector for NetSuite.
Origin of the corresponding object in NetSuite. Only available if you have installed the Zuora Connector for NetSuite.
Date when the refund was synchronized with NetSuite. Only available if you have installed the Zuora Connector for NetSuite.
Specifies whether the refund should be synchronized with NetSuite. Only available if you have installed the Zuora Connector for NetSuite.