POST /v1/payment-methods

You can use this operation to create either a payment method associated with a specific customer account, or an orphan payment method that is not associated with any customer account. The orphan payment method must be associated with a customer account within 10 days. Otherwise, it will be deleted.

To view the applicable fields for each payment method type, select the payment method type from the type list. The following types of the payment methods are supported:

CreditCard - Credit card payment method.
CreditCardReferenceTransaction - Credit Card Reference Transaction. See Supported payment methods for payment gateways that support this type of payment method.
ACH - ACH payment method.
SEPA - Single Euro Payments Area.
Betalingsservice - Direct Debit DK.
Autogiro - Direct Debit SE.
Bacs - Direct Debit UK.
Becs - Direct Entry AU.
Becsnz - Direct Debit NZ.
PAD - Pre-Authorized Debit.
PayPalCP - PayPal Commerce Platform payment method. Use this type if you are using a PayPal Commerce Platform Gateway instance.
PayPalEC - PayPal Express Checkout payment method. Use this type if you are using a PayPal Payflow Pro Gateway instance.
PayPalNativeEC - PayPal Native Express Checkout payment method. Use this type if you are using a PayPal Express Checkout Gateway instance.
PayPalAdaptive - PayPal Adaptive payment method. Use this type if you are using a PayPal Adaptive Payment Gateway instance.
AdyenApplePay - Apple Pay on Adyen Integration v2.0. See Set up Adyen Apple Pay for details.
AdyenGooglePay - Google Pay on Adyen Integration v2.0. See Set up Adyen Google Pay for details.
GooglePay - Google Pay on Chase Paymentech Orbital gateway integration. See Set up Google Pay on Chase for details.

You can also specify a custom payment method type. See Set up custom payment gateways and payment methods for details.

Servers

https://rest.test.zuora.com
https://rest.sandbox.na.zuora.com
https://rest.apisandbox.zuora.com
https://rest.na.zuora.com
https://rest.zuora.com
https://rest.test.eu.zuora.com
https://rest.sandbox.eu.zuora.com
https://rest.eu.zuora.com

Request headers

Name	Type	Required	Description
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/json"
`Content-Encoding`	String	No	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.
`Zuora-Track-Id`	String	No	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 (`'`).
`Authorization`	String	No	The value is in the `Bearer {token}` format where {token} is a valid OAuth token generated by calling Create an OAuth token.
`Idempotency-Key`	String	No	Specify a unique idempotency key if you want to perform an idempotent POST or PATCH request. Do not use this header in other request types. With this header specified, the Zuora server can identify subsequent retries of the same request using this value, which prevents the same operation from being performed multiple times by accident.
`Zuora-Entity-Ids`	String	No	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 do not need to set this header.
`Zuora-Org-Ids`	String	No	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. If the header is not set, the operation is performed in scope of the user's accessible orgs.
`Accept-Encoding`	String	No	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.

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.