CRUD: Retrieve a payment method snapshot
This REST API reference describes how to retrieve a Payment Method Snapshot.
A Payment Method Snapshot is a copy of the particular Payment Method used in a transaction. If the Payment Method is deleted, the Payment Method Snapshot continues to retain the data used in each of the past transactions.
Notes
The following Payment Method fields are not available in Payment Method Snapshots:
ActiveAchAddress1AchAddress2CreatedByIdCreatedDateUpdatedByIdUpdatedDate
The Payment Method Snapshot field PaymentMethodId is not available in Payment Methods.
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.
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.
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 (').
The minor API version.
For a list of available minor versions, see API upgrades.
Query parameters
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 nine-digit routing number or ABA number used by banks. Applicable to ACH payment methods.
This is a masked displayable version of the ACH account number, used for security purposes. For example: XXXXXXXXX54321.
This is a masked displayable version of the bank account number, used for security purposes. For example: XXXXXXXXX54321.
Specifies the type of direct debit transfer. The value of this field is dependent on the country of the user.
Possible Values:
-
AutomatischIncasso(NL) -
LastschriftDE(Germany) -
LastschriftAT(Austria) -
DemandeDePrelevement(FR) -
DirectDebitUK(UK) -
Domicil(Belgium) -
LastschriftCH(CH) -
RID(Italy) -
OrdenDeDomiciliacion(Spain) -
Autogiro(Sweden) -
Betalingsservice(Denmark)
The two-letter country code of the customer’s address. Applicable to direct debit payment methods.
The billing address’s state. Applicable if CreditCardCountry is either Canada or the US.
The session ID of the user when the PaymentMethod was created or updated.
The date when the mandate was created, in yyyy-mm-dd format. A mandate is a signed authorization for UK and NL customers. Only applicable to direct debit payment methods.
The date when the mandate was last updated, in yyyy-mm-dd format. A mandate is a signed authorization for UK and NL customers. Only applicable to direct debit payment methods.
Specifies the PayPal gateway: PayFlow Pro (Express Checkout) or Adaptive Payments.