param_supportedTypes

Optional

Overrides the credit card "Accepted Types" set up for your payment gateway. Supported values are:

• Visa

• MasterCard

• AmericanExpress

• Discover

• Dankort

• JCB

Specify a comma-separated list of values with no space in between, e.g., "AmericanExpress, Visa, MasterCard". Payment Page displays the specified credit card type icons in the order given in the value.

If you do not specify this parameter, the credit card "Accepted Types" displays the following credit card types by default:

• Visa

• Mastercard

• Discover

cityBlackList

Optional

Used to block end users in blacklisted cities from creating credit card payment methods. If end users specify blacklisted cities in the City field when entering their credit card information, an error message is displayed and the payment method cannot be created.

You can also localize the blacklist cities and error messages.

cityWhiteList

Optional

Used to always allow end users in whitelisted cities to create credit card payment methods.

You can also localize the whitelisted cities and error messages.

pmId

Optional

Used to allow end customers to view and enter their existing credit card payment method information, such as the expiration date, CVC code and address information, and re-authenticate the credit card upon submission.

Except for card number and cardholder name, all other credit card fields are available for editing in the Payment Pages 2.0 iFrame form.

If an orphan payment method is associated with a billing account during re-authentication and if checkDuplicated is set to true, Zuora checks the active and closed payment methods associated with the same billing account to ensure that no duplicate payment methods are created.

Payment Pages 2.0 iFrame is PCI compliant. The card information can not be fraudulently edited outside.

This field maps to the refId field in the response.

screeningAmount

Optional

For Chase Paymentech Orbital Gateway integrations, if the Safetech Fraud service is enabled, you can use the screeningAmount field to pass in the amount used for fraud screening for Credit Card validation transactions.

Two-decimal amount is supported.

If screeningAmount is not specified, the authorization amount is used for fraud screening.