Request to Link an Existing Wallet (Consent Step 1)
B2B - Users
Request to Link an Existing Wallet (Consent Step 1)
Starts the consent flow for gaining operating rights on a customer’s existing wallet that belongs to another merchant. A one-time code is SMSed to the customer’s phone; the customer shares it with you to approve. Complete with POST /v1/users/link/confirm.
Use this when POST /v1/users/provision returns LINK_REQUIRED. Wallets are system-wide, but originating money-out actions requires the customer’s consent to add your business as an operator.
POST
Request to Link an Existing Wallet (Consent Step 1)
Authorizations
Your Rach B2B API key. Use rach_sk_live_* for production (on-chain) or rach_sk_test_* for sandbox (no-chain simulation).
Body
application/json
Customer phone number
Example:
"+2250700000001"

