Send money
Send Cobru balance to another Cobru user.
This contract comes from legacy Cobru materials. Re-verify the exact request and response payload in sandbox before using it in a production transfer workflow.
Endpoint
POST https://dev.cobru.co/send/
Content-Type: application/json
Authorization: Bearer <access_token>Requirements
- the sender must have verified email and phone
- the recipient is identified by
username, for exampleMY_BRAND-3001234567 - the amount is debited from the authenticated user's available balance
Request fields
| Field | Type | Required | Description |
|---|---|---|---|
toUser | string | yes | Username that will receive the money. Example: MY_BRAND-3001234567. |
amount | number | yes | Amount to send. Example: 99000. |
Earlier materials also reference to_user. Confirm with Cobru which alias is active for
your integration before going to production.
Example body
{
"toUser": "MY_BRAND-3001234567",
"amount": 99000
}Email and phone confirmation
Before sending money, the sender must have both email and phone in a verified state. First, request the confirmation codes:
POST http://dev.cobru.co/request_confirmation/
Content-Type: application/json
Authorization: Bearer <access_token>| Field | Type | Description |
|---|---|---|
phone | boolean | Indicates whether the code will be sent to the phone. |
email | boolean | Indicates whether the code will be sent to the email address. |
Then make one call for each channel.
Confirm email
POST http://dev.cobru.co/verify_email/
Content-Type: application/json
Authorization: Bearer <access_token>| Field | Type | Description |
|---|---|---|
code | integer | Code received by email. |
Confirm phone
POST http://dev.cobru.co/verify_phone/
Content-Type: application/json
Authorization: Bearer <access_token>| Field | Type | Description |
|---|---|---|
code | integer | Code received by phone. |
Production notes
- Validate sender KYC and account readiness before exposing this action in UI.
- The public materials do not confirm whether transfers are synchronous, queued, or reversible.
- Treat transfer success as untrusted until you can reconcile it through
GET /send/or a downstream ledger.