home

Zuora Payments

Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies
Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies

Welcome to Zuora Product Documentation

Explore our rich library of product information

Show Contents

thumbnailZuora Payments

Braintree Payment Gateway

Set up and configure a Braintree gateway instance

Set up and configure a Braintree gateway instance by using the information in this article, including configuration procedure, descriptions of the configuration fields, and reference for testing the payment gateway.

Prerequisites

Enable the Braintree payment gateway integration for your tenant. See Enable payment gateway integrations for your tenant for instructions.

Configuration fields

Common configuration fields

You must configure some common fields in the Basic Information area for every gateway configuration. See Setting Up Payment Gateways for information on these fields:

  • Name

  • Use Gateway Test Environment

  • Cards Accepted

  • Default Authorization Amount : The default amount cannot be overridden. The validation amount is determined by Braintree.

  • Verify new payment method (optional)

  • Verify updated payment method (optional)

Specific configuration fields

In addition to the common fields, you should specify the following fields:

  • Merchant Id : A unique identifier for your gateway account

  • Merchant Account Id : You can have multiple merchant accounts to process transactions for different businesses or currencies within your Braintree gateway. Each merchant account will be associated with a unique merchant account ID.

  • Public Key : User-specific public identifier

  • Private Key : User-specific secure identifier that should not be shared

  • Soft Descriptor (Optional): The specified value for this field will be presented on customers’ credit card statements. It corresponds to the descriptor field on the Braintree side. See Braintree's documentation for more information.

  • 3DS2 Challenge Requested (Optional): By selecting this setting, if 3DS2 is enabled in the Payment Pages settings, the challengeRequested: true indicator will be passed to the Braintree gateway to request the cardholder challenge. The 3DS2 authentication challenge will be enforced if possible. Ultimately, it is the issuing bank that determines whether a card needs to be authenticated through a challenge.

Test the configuration

For basic guidance on how to test payment gateway integrations within a sandbox environment, see Test payment gateway integration .

You can use the test card information and testing scenarios provided by the gateway vendor to test your integration. See Testing and Go Live in Braintree Developer Docs for details.

Overview of payment gateway integration for Braintree

Last updated: February 19, 2026