You are building Reach for Watch for
A backend in Java, .NET, Node.js, PHP, Python or Ruby That language's server SDK, configured with the environment, merchant ID, public key and private key. The private key stays in server config. Keep the SDK version current, since that's how you get API changes.
A backend in another language, or a team that already works in GraphQL The GraphQL API: one POST endpoint, payments.braintree-api.com/graphql, with payments.sandbox.braintree-api.com/graphql for testing. Auth is Basic with public:private Base64-encoded, and every request needs a Braintree-Version header holding a date like 2019-01-01.
A card form on the web The JavaScript SDK components, such as Hosted Fields, which keep card inputs in iframes Braintree hosts. Drop-in is deprecated. Our Braintree hub covers what moving off it involves. A native iOS or Android app Braintree's mobile SDKs, which take the same client token your server already generates. The app still sends the nonce to your server. Charging never happens from the device.
Server SDK code moving to GraphQL A gradual move, one operation at a time. IDs aren't interchangeable. Braintree's migration guide has a section on legacy versus GraphQL IDs, so plan for stored transaction IDs.