Migrate off Braintree

Migrate off Braintree without touching your card file

Braintree payment methods are PayPal-ecosystem bound. Veliro tok_* under your TRID free card-on-file from Braintree vault lock-in while you keep or leave PayPal wallet flows separately.

Braintree (PayPal) is ubiquitous in US e-commerce and marketplaces. Vaulted payment methods and nonce-based flows excel on Braintree rails, but cards stored only in Braintree do not authorize elsewhere. PayPal corporate roadmap changes are another reason custody should not equal routing.

Veliro separates card credentials from Braintree’s vault. Network tokens under your TRID (with PAN fallback where needed) store as tok_* in your database. Braintree remains a forward target via connection type braintree with merchant ID and keys until you route elsewhere.

Many merchants keep PayPal wallet buttons on Braintree while moving card-on-file to Veliro. Wallets follow PSP wallet rules; cards follow your TRID. That split is intentional and avoids forcing PayPal users through a migration they do not need.

Marketplace models with Braintree sub-merchant accounts need clear mapping: platform tok_* under the platform Veliro merchant_id versus per-seller custody; decide with counsel and your MCC model before cutover.

Migration phases

  1. Separate wallet vs card flows

    Tag customers with payment type: PayPal wallet (stay on Braintree/PayPal) vs card-on-file (migrate to tok_*). Migration scope is cards only unless you explicitly move wallets.

  2. Provision via Secure Fields

    New cards become tok_*; retire Braintree nonce storage for card-on-file in application code.

  3. Register replacement acquirer

    Add Stripe or Worldpay connection for card forward. Test recurring jobs with fresh cryptograms.

  4. Migrate billing cohorts

    Update subscription workers to forward with new connection_id. Braintree connection handles stragglers until drained.

  5. Decommission Braintree card vault

    Disable Braintree connection for card traffic; keep Braintree SDK only if PayPal wallet remains a product requirement.

Common pitfalls

  • Migrating PayPal wallet users who never stored a card on file.
  • Sub-merchant credential confusion in marketplace billing; map legal entity before forward.
  • Braintree test sandbox behavior diverging from production on tokenized MIT; validate in staging with real cryptogram TTL discipline.

Plan your Braintree cutover.

Same tok_* on the next acquirer, no card re-collection campaign. Talk to us about cohort sizing and sandbox forward tests.