B1 for companies
Connect to your customer's B1.
Use the existing B1 wallet through this dedicated service. Each customer approves your company and controls how much it can spend.
Company payments are awaiting activation. Wallet sign-in, balance and activity are available on this host.
How a connection works
- Register your company with the B1 administrator.
- The customer approves your company in their wallet, with a spending limit and expiry.
- Store the customer's approved credential on your server.
- Check available B1, submit an authorized charge, and save its receipt.
API endpoints on this host
| Endpoint | Purpose |
|---|---|
GET /v1/balance | Available B1 and permission remaining |
POST /v1/spend | Charge the approved wallet |
POST /v1/transaction | Look up your customer's receipt |
One reference for each payment
POST /v1/spend
Authorization: Bearer <customer-approved credential>
Content-Type: application/json
{"amountB1":"0.025","reference":"order-unique-123"}Retry the same reference after a timeout. A completed payment is returned without another debit. Changing the amount for that reference is rejected.
402 means insufficient B1 or an exhausted spending limit. Pause the paid service until the customer tops up or changes their authorization. The application must keep account recovery, existing records and essential emergency information accessible.
429 means your company has reached its request limit. Wait for the number of seconds in the Retry-After header, then retry the same payment reference. The initial limit is 120 requests per 60-second window, shared across your company's customer credentials and endpoints.
Credentials belong in server settings, never in browser code, social-media links or URLs. Requests cannot specify another customer's wallet.