Creating your Embedded Partner Merchant Accounts

🚧

Before you start

Before proceeding, ensure your Embedded Partner Account is fully set up with the necessary parent API keys. If this step is incomplete, please revisit the initial setup process.

Integrating BVNK's embedded payment solutions requires completing several straightforward steps to enable secure and efficient transactions for your Embedded Partner Merchants (EPMs).

Key Steps to Activate Your Embedded Partner Merchant Accounts

The process encompasses several critical configurations:

1. API Authentication: Secure your API communications by generating API keys and configuring Hawk Authentication headers. This ensures all requests to BVNK are authenticated, protecting data integrity.
2. Webhook Implementation: Set up a webhook listener to receive and authenticate real-time notifications from BVNK. This keeps your system updated with transaction statuses and events.
3. Agreement Compliance: Before activating EPM accounts, present and obtain acceptance of BVNK’s agreements from your merchants. This step is crucial for legal compliance and informed consent.
4. EPM Account Activation: Activate EPM accounts through the BVNK portal, enabling your merchants to access BVNK’s payment ecosystem. This step involves creating merchant accounts under the 'Manage Merchants' section.
5. Wallet Configuration: Configure wallets for EPM accounts to manage assets securely. Specify currency types and transactional capabilities for each wallet, using the BVNK API for setup.
6. Merchant ID Setup: Generate Merchant IDs (MIDs) for transaction processing. MIDs link transactions to the merchant's wallet, facilitating payments in and out. Create MIDs via the 'Manage Merchants' section.

Following these steps precisely equips your EPM accounts for secure and efficient operations within the BVNK payment ecosystem, ensuring a smooth integration process.

📘

By concluding this guide, you will secure the accountReference for your EPM account. This identifier is vital for directing API calls accurately by including it in the x-account-reference header of your requests, ensuring operations impact the intended account.