| account_key |
str |
Internal ID of the customer account that will own the payment method. To create an orphan payment method that is not associated with any customer account, you do not need to specify this field during creation. However, you must associate the orphan payment method with a customer account within 10 days. Otherwise, this orphan payment method will be deleted. |
[optional] |
| payment_method_number |
str |
To avoid the repetitive creation of identical payment methods, you can associate a unique identifier with the payment method. You can specify a string within the allowed limits, or if none is provided, the system will automatically generate one for the payment method. |
[optional] |
| payment_gateway_number |
str |
The natural key for the payment gateway. |
[optional] |
| screening_amount |
float |
For Chase Paymentech Orbital Gateway integrations, if the Safetech Fraud service is enabled, use this field to pass in the amount used for fraud screening for Credit Card validation transactions. Two-decimal amount is supported. If the `screeningAmount` field is not specified, the authorization amount is used for fraud screening. |
[optional] |
| auth_gateway |
str |
Internal ID of the payment gateway that Zuora will use to authorize the payments that are made with the payment method. If you do not set this field, Zuora will use one of the following payment gateways instead: * The default payment gateway of the customer account that owns the payment method, if the `accountKey` field is set. * The default payment gateway of your Zuora tenant, if the `accountKey` field is not set. |
[optional] |
| gateway_options |
GatewayOptions |
|
[optional] |
| ip_address |
str |
The IPv4 or IPv6 information of the user when the payment method is created or updated. Some gateways use this field for fraud prevention. If this field is passed to Zuora, Zuora directly passes it to gateways. If the IP address length is beyond 45 characters, a validation error occurs. For validating SEPA payment methods on Stripe v2, this field is required. |
[optional] |
| make_default |
bool |
Specifies whether the payment method will be the default payment method of the customer account that owns the payment method. Only applicable if the `accountKey` field is set. When you set this field to `true`, make sure the payment method is supported by the default payment gateway. |
[optional] [default to False] |
| processing_options |
PaymentMethodRequestProcessingOptions |
|
[optional] |
| skip_validation |
bool |
Specify whether to skip the validation of the information through the payment gateway. For example, when migrating your payment methods, you can set this field to `true` to skip the validation. |
[optional] [default to False] |
| type |
str |
Type of the payment method. Possible values include: * `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 Complete Payments payment method. Use this type if you are using a PayPal Complete Payments 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. Note that Zuora is continuously adding new payment method types. |
|
| currency_code |
str |
The currency code of the payment method. |
[optional] |
| tokenize |
bool |
Specifies whether to tokenize the payment method. |
[optional] [default to False] |
| tokens |
PaymentMethodRequestTokens |
|
[optional] |
| baid |
str |
ID of a PayPal billing agreement. For example, I-1TJ3GAGG82Y9. |
|
| email |
str |
Card holder's email address, 80 characters or less. |
|
| preapproval_key |
str |
The PayPal preapproval key.. |
|
| card_holder_info |
CreateCreditCardReferenceCardholderInfo |
|
[optional] |
| card_number |
str |
Credit card number. This field is required if `type` is set to `CreditCard`. However, for creating tokenized credit card payment methods, this field is optional if the `tokens` and `cardMaskNumber` fields are specified. |
[optional] |
| card_mask_number |
str |
The masked card number associated with the credit card payment. This field is only required if the credit card payment method is created using tokens. |
[optional] |
| card_type |
str |
The type of the credit 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. |
|
| identity_number |
str |
The identity number of the customer. |
|
| mandate_info |
PaymentMethodRequestMandateInfo |
|
[optional] |
| check_duplicated |
bool |
Indicates whether the duplication check is performed when you create a new credit card payment method. The default value is `false`. With this field set to `true`, Zuora will check all active payment methods associated with the same billing account to ensure that no duplicate credit card payment methods are created. An error is returned if a duplicate payment method is found. The following fields are used for the duplication check: - `cardHolderName` - `expirationMonth` - `expirationYear` - `creditCardMaskNumber`. It is the masked credit card number generated by Zuora. For example: ``` ************1234 ``` |
[optional] |
| expiration_month |
int |
One or two digit expiration month (1-12) of the credit card. This field is required if `type` is set to `CreditCard`. However, for creating tokenized credit card payment methods, this field is optional if the `tokens` and `cardMaskNumber` fields are specified. |
[optional] |
| expiration_year |
int |
Four-digit expiration year of the credit card. This field is required if `type` is set to `CreditCard`. However, for creating tokenized credit card payment methods, this field is optional if the `tokens` and `cardMaskNumber` fields are specified. |
[optional] |
| mit_consent_agreement_ref |
str |
Specifies your reference for the stored credential consent agreement that you have established with the customer. Only applicable if you set the `mitProfileAction` field. |
[optional] |
| mit_consent_agreement_src |
StoredCredentialProfileConsentAgreementSrc |
|
[optional] |
| mit_network_transaction_id |
str |
Specifies the ID of a network transaction. Only applicable if you set the `mitProfileAction` field to `Persist`. |
[optional] |
| mit_profile_action |
StoredCredentialProfileAction |
|
[optional] |
| mit_profile_agreed_on |
date |
The date on which the profile is agreed. The date format is `yyyy-mm-dd`. |
[optional] |
| mit_profile_type |
StoredCredentialProfileType |
|
[optional] |
| security_code |
str |
CVV or CVV2 security code of the credit card. To ensure PCI compliance, this value is not stored and cannot be queried. |
[optional] |
| cryptogram |
str |
Cryptogram value supplied by the token provider if DPAN or network scheme token is present To ensure PCI compliance, this value is not stored and cannot be queried. |
[optional] |
| credit_card_mask_number |
str |
The masked credit card number, such as: ``` *********1112 ``` This field is specific for the CC Reference Transaction payment method. It is an optional field that you can use to distinguish different CC Reference Transaction payment methods. Though there are no special restrictions on the input string, it is highly recommended to specify a card number that is masked. |
[optional] |
| second_token_id |
str |
A gateway unique identifier that replaces sensitive payment method data. `secondTokenId` is conditionally required only when `tokenId` is being used to represent a gateway customer profile. `secondTokenId` is used in the CC Reference Transaction payment method. |
[optional] |
| token_id |
str |
A gateway unique identifier that replaces sensitive payment method data or represents a gateway's unique customer profile. `tokenId` is required for the CC Reference Transaction payment method. When `tokenId` is used to represent a customer profile, `secondTokenId` is conditionally required for representing the underlying tokenized payment method. The values for the `tokenId` and `secondTokenId` fields differ for gateways. For more information, see the Knowledge Center article specific to each gateway that supports the CC Reference Transaction payment method. Note: When creating an ACH payment method, if you need to pass in tokenized information, use the `mandateId` instead of `tokenId` field. |
|
| mandate_id |
str |
The mandate ID. When creating an ACH payment method, if you need to pass in tokenized information, use the `mandateId` instead of `tokenId` field. |
[optional] |
| mandate_received_status |
PaymentMethodMandateInfoMandateStatus |
|
[optional] |
| existing_mandate_status |
PaymentMethodMandateInfoMandateStatus |
|
[optional] |
| mandate_creation_date |
date |
The date on which the mandate was created. |
[optional] |
| mandate_update_date |
date |
The date on which the mandate was updated. |
[optional] |
| address_line1 |
str |
First address line, 255 characters or less. |
[optional] |
| address_line2 |
str |
Second address line, 255 characters or less. |
[optional] |
| bank_aba_code |
str |
The nine-digit routing number or ABA number used by banks. |
|
| bank_account_name |
str |
The name of the account holder, which can be either a person or a company. For ACH payment methods on the BlueSnap integration, see Overview of BlueSnap gateway integration for more information about how Zuora splits the string in this field into two parts and passes them to BlueSnap's `firstName` and `lastName` fields. |
|
| bank_account_number |
str |
The bank account number associated with the ACH payment. This field is only required if the `type` field is set to `ACH`. However, for creating tokenized ACH payment methods on Stripe v2, this field is optional if the `tokens` and `bankAccountMaskNumber` fields are specified. |
[optional] |
| bank_account_mask_number |
str |
The masked bank account number associated with the ACH payment. This field is only required if the ACH payment method is created using tokens. |
[optional] |
| bank_account_type |
PaymentMethodPADBankAccountType |
|
|
| bank_name |
str |
The name of the bank where the ACH payment account is held. 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 a dummy value. |
|
| city |
str |
City, 40 characters or less. 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. |
[optional] |
| country |
str |
Country, must be a valid country name or abbreviation. See Country Names and Their ISO Standard 2- and 3-Digit Codes 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. |
[optional] |
| phone |
str |
Phone number, 40 characters or less. |
[optional] |
| state |
str |
State, must be a valid state name or 2-character abbreviation. See United States Standard State Codes and Canadian Standard Province Codes for the list of supported names and abbreviations. |
[optional] |
| zip_code |
str |
Zip code, 20 characters or less. |
[optional] |
| account_holder_info |
CreatePaymentMethodBankTransferAccountHolderInfo |
|
|
| bank_code |
str |
The sort code or number that identifies the bank. |
|
| account_number |
str |
The number of the customer's bank account. |
|
| branch_code |
str |
The branch code of the bank used for direct debit. |
|
| account_mask_number |
str |
The sort code or number that identifies the bank. This is also known as the sort code. |
[optional] |
| iban |
str |
The International Bank Account Number. |
[optional] |
| business_identification_code |
str |
The BIC code used for SEPA. |
[optional] |