Payment Token Migration to Braintree

VIDEO TRANSCRIPT | Recorded: 2025-10-06 | Verify against current system state

Abstract¶

Technical knowledge transfer on payment token migration from BluePay (CardConnect/Fiserve) to Braintree (PayPal). Covers vendor naming conventions, why migration is necessary (Chargent's BluePay integration required full card storage violating PCI compliance), how migration works through secure three-party file transfer, token location in Salesforce/Braintree/BluePay, payment method consolidation from Aptify, refund handling decision, and testing strategy using limited production test transactions.

Key Procedures¶

• Identify active auto renewal transactions for token migration (exclude 3-month history)
• Provide transaction list to BluePay for secure export to Braintree
• Braintree imports tokens with order ID for mapping back to Salesforce
• Update token in Salesforce: Chargent Tokens (payment method), Chargent Order, Chargent Transaction
• Consolidate Aptify payment methods (1 per person per card vs 1 per order)
• Process refunds manually via BluePay for 3-month transition period
• Test token processing in sandbox by replacing BluePay token with Braintree token
• Verify auto renewal can process with new token overnight

Notable Statements¶

• 0:00:21 "We are migrating payment tokens from BluePay, which is also known as CardConnect, which is also known as Fiserve, over to Braintree and PayPal."
• 0:01:52 "Aptify has a direct relationship with BluePay. Our contract actually goes through Aptify for BluePay."
• 0:05:17 "The BluePay integration required us to store full card data in the system, not just a token. That's a really high risk for PCI compliance."
• 0:05:48 "We chose Braintree because we already had that relationship set up because we're working with PayPal Payflow Pro."
• 0:08:59 "Payment methods in Aptify are just not unique at all. Even if you've used the card 50 times, 50 payment methods are created."
• 0:09:44 "Unless we request the flag be set in Braintree, refunds will not work from imported tokens."
• 0:10:15 "We're basically just allowing each card to be refunded... even if they haven't paid that much money" - Re: refund risk
• 0:16:04 "There are multiple places where the token is going to have to be updated."

Systems & Configurations¶

Systems Mentioned¶

• BluePay (current payment gateway via Aptify)
• CardConnect / Fiserve (BluePay parent companies)
• Braintree (new payment gateway for Salesforce)
• PayPal Payflow Pro (conference transactions)
• Salesforce (new AMS)
• Chargent (payment processing app for Salesforce)
• Aptify (legacy AMS)

Specific Configurations¶

Credentials/Access Mentioned¶

• Braintree portal login (shared with conference transactions)
• Braintree sandbox access needed for Matt
• BluePay portal login

Errors & Troubleshooting¶

• Issue: Chargent BluePay integration requires full card storage
• Cause: BluePay direct integration not token-based
• Resolution: Migrate to Braintree which supports token-only storage

• Timestamp: 0:05:17

• Issue: Aptify creates duplicate payment methods per order

• Cause: Payment method not consolidated per card
• Resolution: Script consolidates to 1 payment method per person per card type/number

• Timestamp: 0:09:23

• Issue: Refunds risky from imported tokens

• Cause: Could refund more than originally charged
• Resolution: Handle refunds manually via BluePay for 3-month period

• Timestamp: 0:09:44

• Issue: Limited test transactions available

• Cause: Production data required; testing uses real cards
• Resolution: Use internal staff cards, careful test planning
• Timestamp: 0:10:28

Transcript Gaps & Quality Notes¶

• Knowledge transfer session for Matt (new team member)
• Screen shares of Salesforce token locations, Braintree portal, BluePay portal
• Migration currently on pause; documentation being consolidated
• Next steps: verify sample file contents, document exact field update requirements
• Jeff to package all migration notes and email threads for handoff