Partner overview

Use the Partner product when you distribute Bit2Me to your customers. You hold parent API keys. Each end user is one subaccount.

This page describes the published API. It is not legal advice. Bit2Me Legal and Compliance must review KYC, KYB, Travel Rule, and 2FA copy before this portal is announced to partners.

Journeys

KYC (natural person)

Eight steps to verified and tier: 2. Hosted ID + liveness only.

KYB (company)

Company subaccount and document pack. No identity webview.

Widgets

Identity in a native browser. Add card in a WebView.

Funding

Bank, card, Apple Pay, Google Pay, and Teller / Paylands rails in your contract.

Withdrawals

Verify the destination wallet, then draft and accept. Address book is the target path.

Travel Rule

POST /v2/blockchain-manager/travel-rule-order — not Embed report.

Transfers

Social Pay to a Bit2Me user (email, phone, alias). Last mile: Argentina only. Or pocket-to-pocket.

Rules that prevent tickets

One end user = one subaccount. Send X-SUBACCOUNT-ID after create.
Do not treat the user as live until KYC status: verified and tier: 2 (persons).
Do not call identity init on type: company.
The first time a subaccount sends crypto to a new blockchain address, verify that destination with 2FA before you withdraw. Later sends to the same addressBookId reuse it.
Address-book withdrawals carry Travel Rule data on the entry: do not call travel-rule-order there. On Wallet legacy, submit Travel Rule when the operation returns pending_user_information. Do not use Embed report for this.
Pay another Bit2Me user with Social Pay (email / phone / alias). Local last mile is Argentina only.
Convert EUR/crypto on Pro: First order documents Wallet deposit and withdraw.
There is no sandbox API host. Use production gateway URLs and Get API keys.
Apple Pay must leave the in-app WebView.