Supported payment methods

BlueSnap supports the following payment methods:

• ACH

• SEPA

• Credit Card/Gift Card/Prepaid Card, including:

  • Visa

  • Mastercard

  • Discover

  • American Express

  • JCB (in select countries)

  • Diners Club

  • Elo

  • Hipercard

  • Argencard

  • Cabal

  • Cencosud

  • Nativa

  • Tarjeta Naranja

  • Tarjeta Shopping

  • Cartão MercadoLibre

• Google Pay

• Apple Pay

  Note:

  • For Apple Pay and Google Pay, collecting payment method information and processing payments are not supported through the Payment Pages 2.0 solution. To build checkout experiences for these payment methods, set up Apple Pay or Google Pay through the JavaScript SDK integration or the Payment Form solution.

  • For Google Pay, the configured currency must match the currency in the transaction request. Any mismatch results in an error, and the transaction is rejected.

For more information about setting up payment methods in Zuora, see Define and set up payment methods .

Supported payment operations

The following payment operations are available through BlueSnap:

• Payment: The Soft Descriptor field is also supported if you create a SEPA payment.

• Full Refund: For SEPA refunds, it takes about 7 days for a SEPA payment to reach a stage when it can be refunded.

• Multiple, Partial Refund (Referenced Refund) BlueSnap's API supports only the first partial refund. An error will occur if attempting to refund multiple partials. BlueSnap Support team can be contacted to handle this scenario.

• Create a payment method

• Verify a payment method

• Create Authorization

• Void/Capture an Authorization

• Create a Payment

Support for 3D Secure 2.0

See Enable 3DS2 for BlueSnap gateway integration and Zuora’s implementation of 3D Secure 2.0 for more information.

Support for Level 2 and Level 3 card data processing

The BlueSnap gateway integration supports processing Level 2 and Level 3 credit card data. For more information, see the following articles:

• Set up and configure a BlueSnap gateway instance

• Level 2 and Level 3 Card Data

Support for stored credential profiles

BlueSnap gateway includes support for the Stored Credential Transactions framework and the sharing NTI feature. For details, see Support for stored credential transactions overview .

Support for Gateway Reconciliation

The BlueSnap gateway integration supports the following Gateway Reconciliation event types for ACH transactions:

• Payment Settlement

• Payment Rejection

• Payment Chargeback

• Refund Settlement

For refund transactions, the BlueSnap gateway integration only supports the settlement event. The refunds in the Rejected status are ignored.

The reconciliation job retrieves the reconciliation report from the BlueSnap gateway daily at 3:00 pm PST. It usually takes 3-10 days for these endpoints to be updated with the status of the transaction.

For more information about enabling and configuring the Gateway Reconciliation service, see the following articles:

• Gateway Reconciliation

• Set up and configure a BlueSnap gateway instance

Support for Payment Method Updater

To set up the BlueSnap Payment Method Updater service in Zuora, see Configure BlueSnap Payment Method Updater for more information.

Supported Gateway Options fields

If the support for Level 2 or Level 3 data processing is enabled, you can submit additional information to the BlueSnap gateway using gateway options. Currently, BlueSnap gateway integration supports the following gateway option fields:

• InvoiceNum

• TaxSum

• TransactionOrderSource : To indicate that the current transaction is a MOTO payment transaction, specify MOTO for this field. If you want to configure a gateway instance, through which all transactions will be processed as MOTO transactions, see Transaction Order Source configuration field .

You can use these fields in Payment Pages 2.0 or the following REST API operations:

• Create a payment

• Create a payment method

• Refund a payment

All Gateway Options fields are string fields.

Limitations

BlueSnap gateway integration does not support non-referenced refunds.

Payer Name Extraction

While Zuora stores the name of a credit card payment method as a single string, e.g., "John Smith", BlueSnap requires that the first name and last name are sent as two separate fields. To conform to BlueSnap's requirement, Zuora extracts the first name and last name from the single name string. BlueSnap recommends splitting the name by the first space character.

For ACH payment methods, Zuora splits the string specified in the account holder name field into two parts at the first space from the left. The first part will be passed to BlueSnap and populated in the firstName field. The second part will be passed and populated in the lastName field. The limit is 25 characters for both fields according to BlueSnap PayerInfo documentation . For example, if Axxxxxxx Bxxxxxxx Cxxxxxx Dxxx Exx is specified, Axxxxxxx is firstName and Bxxxxxxx Cxxxxxx Dxxx Exx is lastName .

To add an ACH payment method to a Business Checking type of account, the payerInfo > companyName field must be included in the request to the gateway. You can pass in the company name through the following approaches. The value passed in will be mapped to the payerInfo > companyName field, in addition to the firsName and lastName fields.

• The Account Holder Name field in Zuora UI

• The Account Holder Name field in Payment Pages

• The bankAccountName field of the Create a payment method REST API operation