Skip to main content

Partner Solution Key

You can process transactions on behalf of merchants who are using your registered solution. To enable merchants to use your solution, you must create a partner solution key. The acquirer you are partnering with must then update the merchant's account to use the key. also authenticates the merchants, ensuring that the registered solution only performs actions authorized by the merchants.

This section explains how you can set up a partner solution key to enable your solutions to process transactions on behalf of merchants.

Partner Solution Types

These are the types of solutions technology partners can register to be used by merchants:

  • API-only integrations
  • Desktop software
  • Hybrid approaches
  • Mobile applications
  • Plugins
  • Terminal integrations
  • Web applications

Benefits

A partner solution key improves your organization's experience by:

  • Reducing the time required to manage API security keys.
  • Managing which endpoints a merchant's transactions can use.
  • Delegating key management to the Technology Partner.
  • Enabling and disabling the web-application from processing transactions.

You must use separate keys for the test and production environments.

Overview

This illustration shows an example of how a partner solution key is used across technology partner and partner reseller organizations.

Overview of Partner Solution Key

A technology partner can have more than one registered solution that is used by multiple transacting merchants. Transacting merchants can use multiple solutions from different technology partners. A technology partner can register a custom solution that is only usable by a specified partner reseller.

To set up a Partner Solution Key as a technology partner, you must complete these tasks.

  1. Onboard as a technology partner with and register your solution.

    For more information about how to become a partner, see Creating a Tech Partner Sandbox in the Partner Getting Started Guide.

    For more information about how to become a partner, see Creating a Tech Partner Sandbox in the Partner Getting Started Guide.

    Contact your account team to begin the technology partner registration process.

  2. Contact your account manager to create a user account.

  3. Create a new P12 certificate to use as the Partner Solution Key.

    For more information, see Create a P12 Certificate.

    For more information, see Create a P12 Certificate.

    For more information, see Create a P12 Certificate.

    For more information, see Create a P12 Certificate.

    Contact your Bank of America Merchant Services account team for guidance on creating a P12 certificate.

  4. Implement the key from your P12 certificate into your system.

    For more information about how to set up your system to support the P12 certificate, see Construct Messages Using JSON Web Tokens in the Getting Started with REST Developer Guide.

    For more information about how to set up your system to support the P12 certificate, see Construct Messages Using JSON Web Tokens in the Getting Started with REST Developer Guide.

    For more information, see Construct Messages Using JSON Web Tokens in the Getting Started with REST Developer Guide.

    For more information, see Construct Messages Using JSON Web Tokens in the Getting Started with REST Developer Guide.

    Contact your Bank of America Merchant Services account team for guidance on implementing JWT authentication with your P12 certificate.

  5. Coordinate with the partner reseller to begin testing transactions.

  6. Contact your account manager to transition your implementation from test to production.

Last published: September 29, 2026