New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingCPQPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Payment Methods


  • Payment Methods Overview
  • Cards
  • Direct Debit
  • Bank Based Payments
  • Wallets
  • Vouchers
  • Articles and FAQ

Payment Gateways and Configuration


  • Payment Gateways Overview
  • Chargebee Test Gateway
  • Stripe
  • PayPal Payment Services
  • Chargebee Pay
  • Adyen
  • Authorize.net
  • Bambora (formerly Beanstream)
  • Bank of America
  • BluePay
  • BlueSnap
  • Braintree
  • Checkout.com
  • CyberSource
  • dLocal
  • EBANX
  • Ecentric
  • Elavon
  • E-xact Direct Integration
  • eWay Rapid
  • Global Payments
  • GoCardless
  • J.P. Morgan Mobility Payment Solutions
  • Metrics Global
  • Mollie
  • Moneris
  • Network Merchants Incorporated (NMI)
  • Nuvei
  • Orbital (Chase Paymentech)
  • Pay.com
  • Paymill
  • Paystack
  • Pin Payments
  • QuickBooks Payments
  • Razorpay
  • Sage Pay
  • Solidgate
  • Tempus
  • Twikey
  • Windcave
  • Worldline Online Payments(formerly Ingenico)
  • Worldpay
  • Articles and FAQ

Level 2/3 Data Support


  • Level 2/3 Data Support

Payment Optimization Engine


  • Overview
  • Defaults
  • Advanced Setup
  • Payment Method Display Rules
  • Verification Rules
  • Routing Rules

Dunning


  • Dunning
  • Articles and FAQ

Offline Checkout


  • Offline Checkout
  • Articles and FAQ

Transaction Sync & Invoice Mapping


  • Transaction Sync and Invoice Mapping

Fraud Management


  • Fraud Management

Error Handling


  • Errors with Root Cause and Troubleshooting

Payment Lifecycle Logs


  • Payment Intents
  • Transactions
  • Gateway Activity Logs
  • Gateway Webhook Logs
  • Articles and FAQ

Others


  • Reach (Merchant of Record)
  • Bulk Deletion of Payment Methods
  • Custom Payment Methods
  • Payment Initiator Parameter
  • PSD2 and Strong Customer Authentication
  • RBI e-Mandate
  • RBI Tokenization Regulations
  • Chargeback Management
  • Transaction Descriptors
  • Payment Preferences
  • Visa Trial Rules
  • Mastercard Trial Rules
  • Co-badged Card Compliance
  • Articles and FAQ
  1. Payments
  2. Payment Gateways and Configuration
  3. Articles and FAQ
  4. Braintree
  1. Payments
  2. Payment Gateways and Configuration
  3. Articles and FAQ
  4. Braintree

Why do Braintree transactions fail with error 2025 (Set Up Error - Merchant)?

Problem statement

Your Braintree transactions fail with error code 2025 or the message Set Up Error - Merchant, and you may receive a Chargebee email asking you to reconnect your Braintree integration — even though Braintree confirms your account is active. This article explains why this happens and how to resolve it.

Solution

Error 2025 is a merchant setup error. It is not a normal card decline, and it is not necessarily a credential or OAuth expiry. The payment fails because of how your Braintree merchant account or gateway setup aligns with what the processor expects.

Common causes:

  • The merchant account is not fully enabled for the payment type or region.
  • The wrong Braintree merchant account is used for the transaction currency.
  • The merchant account has restrictions that block the charge.

Braintree may confirm that your Chargebee OAuth connection is active and that other payments are processing normally, while specific transactions still fail in Chargebee with this error.

To resolve it:

  1. In Chargebee, go to Logs > Transactions and open the failed transactions. Note the Braintree error code and error detail.
  2. Contact Braintree Support with the failed Chargebee transaction IDs, and ask them to review your merchant account configuration.
  3. If you use multiple currencies, verify that each currency is mapped to the correct Braintree merchant account ID in Chargebee. See How do I set up multi-currency pricing with Braintree and Chargebee?.
  4. After Braintree confirms the merchant account is corrected, retry the transaction. The transaction completes successfully once the setup error is resolved.

Additional information

When Chargebee detects repeated failures of this kind, it sends a gateway reconnect email asking you to update your Braintree credentials or connection. The email is triggered by these transaction failures, not by a broken connection. For more context, see Understanding gateway reconnect emails on the Braintree page.

Braintree documents all decline codes in their declines documentation.

Important notes

  • Reconnecting does not fix a merchant setup error. The Reconnect option in Chargebee resolves credential or access issues only. For error 2025, correct the merchant account configuration in Braintree instead.
  • If you configured Braintree through OAuth, Braintree may not show an authorization expiry on their side even when Chargebee sends a reconnect alert based on transaction failures.

Related Articles

Braintree error codes 2015 and 2099
'Error: 91517/91577 Payment instrument is not accepted by this merchant account/merchant account does not support payment instrument. What''s going on?'
'Error: 2046/2038 Declined/Processor Declined. What''s going on?'
Testing with Braintree sandbox.
'Error: 3000 Processor Network unavailable. What''s going on?'
How to configure Braintree with Chargebee?
How do I setup Multi Currency Pricing feature with Braintree and Chargebee?
Can I view Processor Responses in my Braintree account?

Show more

Was this article helpful?