Retrieve a payment method snapshot
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.
Query parameters
The maximum number of results to return in a single page. If the specified pageSize is less than 1 or greater than 99, Zuora will return a 400 error.
A cursor for use in pagination. A cursor defines the starting place in a list. For instance, if you make a list request and receive 100 objects, ending with next_page=W3sib3JkZXJ=, your subsequent call can include cursor=W3sib3JkZXJ= in order to fetch the next page of the list.
A case-insensitive query parameter that specifies the sort order of the list, which can be either ascending (e.g. accountnumber.ASC) or descending (e.g. accountnumber.DESC). You cannot sort on properties in arrays. If the array-type properties are specified for the sort[] parameter, they are ignored.
A case-insensitive filter on the list.
A case-insensitive query parameter that allows you to specify which fields are returned in the response.
Specifies whether to include fields with the null value in the response.
- If set to
true, all fields will be returned in the response, including those with thenullvalue. - If set to
false, only fields with non-null values will be returned.
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 time that the payment method snapshot gets created in the system, in the
YYYY-MM-DD HH:MM:SS format.
The time that the payment method snapshot gets updated in the system, in the
YYYY-MM-DD HH:MM:SS format.
The nine-digit routing number or ABA number used by banks. This field is only required if the type field is set to ACH.
The name of the account holder, which can be either a person or a company. This field is only required if the type field is set to ACH.
The masked bank account number associated with the ACH payment method. This field is only required if the type field is set to ACH.
The type of bank account associated with the ACH payment method. This field is only required if the type field is set to ACH.
When creating an ACH payment method on Adyen, this field is required by Zuora but it is not required by Adyen. To create the ACH payment method successfully, specify a real value for this field if you can. If it is not possible to get the real value for it, specify any of the allowed values as a dummy value, Checking preferably.
Country for the ACH payment method. Must be a valid country name or abbreviation.
See View countries or regions for the list of supported country names and abbreviations.
It is recommended to provide the city and country information when creating a payment method. The information will be used to process payments. If the information is not provided during payment method creation, the city and country data will be missing during payment processing.
State for the ACH payment method. Must be a valid subregion (state or province) name or code. For more information, see View subregions of a specific country or region.
Indicates whether the payment method is a system-generated payment method. This field is for Zuora internal use and does not impact customer integration or use cases.
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 country where the credit card holder stays.
When creating a payment method through a translated UI or Payment Page, a country name in a translated language might be selected. Regardless of the country texts selected when creating the payment method, only the supported country name returns in this field. For a complete list of supported country names, see View countries or regions. Internationalization is not supported for the API field value.
Four-digit expiration year.
The masked credit card number, such as *********1112.
The type of the credit card or debit card.
Possible values include Visa, MasterCard, AmericanExpress, Discover, JCB, and Diners. For more information about credit card types supported by different payment gateways, see Supported Payment Gateways.
Note: This field is only returned for the Credit Card and Debit Card payment types.
The session ID of the user when the PaymentMethod was created or updated.
The number of consecutive failed payments for this payment method. It is reset to 0 upon successful payment.
A gateway unique identifier that replaces sensitive payment method data.
Note: This field is only returned for the Credit Card Reference Transaction payment type.
The type of the payment method. For example, CreditCard.
The identification reference of the custom payment method.
This field should be mapped to a field name defined in the fields array for the purpose of being used as a filter in reporting tools such as Payment Method Data Source Exports and Data Query.
The identification reference of the user or customer account.
This field should be mapped to a field name defined in the fields array for the purpose of being used as a filter in reporting tools such as Data Source Exports and Data Query.
The identification reference indicating the subtype of the custom payment method.
This field should be mapped to a field name defined in the fields array for the purpose of being used as a filter in reporting tools such as Data Source Exports and Data Query.
Other method-specific data of the payment method.