Braintree

Braintree

Govern Braintree with Corma: Account Admin and custom roles, API keys tied to each user, mandatory 2FA, SAML SSO, and SCIM for managed merchants only.

The Corma and Braintree integration keeps access to your Braintree Control Panel in line with the staff who need it. PayPal presents PayPal Braintree as its end-to-end payment platform built for growth, and eBay announced its agreement to acquire Braintree on September 26, 2013. Braintree's US fee page lists a rate per transaction, so the governance question is who can act in the Control Panel and whose API keys keep your checkout running.

Key takeaways

  • Braintree's built-in Account Admin role has the maximum permissions and cannot be edited, and only an Account Admin can grant the Manage Users and Manage Roles permissions.
  • Each Braintree user has their own public and private API keys, and generating new keys leaves the old ones working until they are deleted.
  • Since September 2023, every Braintree user must enable two-factor authentication to access the Control Panel.
  • Braintree supports SAML 2.0 single sign-on, and SCIM provisioning with Okta or Microsoft Entra is open only to managed merchants with a dedicated CSM or TAM.

Why can removing a Braintree user break payments?

API keys belong to people. Braintree's gateway credentials page explains that each user of the gateway has their own set of API keys, which they can change or rotate at any time. Braintree warns that deleting or suspending a user whose API credentials are included in your integration can break your connection to Braintree and cause failed transactions. Suspended users can be reactivated, while deleted users are permanently removed.

That is why Braintree's go-live guide recommends a dedicated API user, set up with an email address that is not associated with a single employee and with Account Admin permissions. Braintree documents no expiry for API keys. Single sign-on has its own gap: without SCIM, a user suspended in the identity provider is denied access but still appears active in the Control Panel until someone suspends or deletes them there.

How Corma governs Braintree

  • Admins under review: Account Admins and custom roles that hold Manage Users or Manage Roles go into automated access reviews.
  • Leavers with an API key check: a leaver workflow in the IT Workflow Builder asks an Account Admin to check whether the person's API keys are used in an integration, then to suspend or delete them in the Control Panel.
  • API user with an owner: the dedicated API user Braintree recommends is a non-human identity, so it needs a named owner on your side.
  • SSO without SCIM covered: without SCIM, the leaver workflow keeps the Control Panel step, since a user suspended in the identity provider still appears active there.

Frequently asked questions

Does Braintree support SSO and SCIM?

Yes, with conditions. Braintree supports SAML 2.0-based single sign-on through your identity provider, requested through your CSM or TAM or through Braintree support. SCIM provisioning, with Okta or Microsoft Entra, is open only to managed merchants, and deleting SSO users cannot be done through Okta's SCIM integration. Read how SCIM and SAML differ.

How does Corma connect to Braintree?

Braintree's API documentation shows no way to list Control Panel users outside SCIM, so Corma's browser-based agents can handle user steps in the Control Panel, in an isolated browser session with credentials taken from your password vault. See also how Corma covers payment platforms such as Adyen.

Where is Corma data hosted?

Corma runs on AWS, with web servers and databases in data centers inside the European Union. Data is encrypted in transit and at rest, and Corma is ISO/IEC 27001:2022 certified.

Want every Braintree leaver checked against the API keys your checkout uses? Book a Corma demo.

Related Integrations

Check out other integrations that could help you on managing your software licences and accesses!