Request Payment
To request a payment address for an invoice, send a POST request to:
POST https://www.mimbla.com/api/v1/merchant/invoice/rp/{invoice_id}
Headers
| Header | Required | Description |
|---|---|---|
MB-API-KEY | Yes | Merchant API key for the business that owns the invoice. |
Accept | Recommended | Use application/json. |
Content-Type | Recommended | Use application/json. |
Request Body
| Parameter | Type | Required | Description |
|---|---|---|---|
crypto | string | Conditional | Required only when the invoice was created with crypto = ALL. Omit this field when the invoice has a fixed crypto. |
Supported crypto symbols include BTC, LTC, BCH, XMR, ETH, BNB, USDT, USDT_ERC20, USDT_BEP20, XAUT, and PAXG.
Behavior
- The invoice must belong to the business represented by
MB-API-KEY. - The invoice status must be
unpaid. - If a payment was already requested for this invoice, the endpoint returns an error.
Example Request
POST https://www.mimbla.com/api/v1/merchant/invoice/rp/Xu9FO0ZF62PA
MB-API-KEY: YOUR_API_KEY
Content-Type: application/json
{
"crypto": "BTC"
}
Example Successful Response
If successful, this endpoint returns 201 Created:
{
"invoice_id": "b7ef89e2-97a2-4b10-973f-a76fd2f5f1a3",
"address": "bc1q...",
"amount": "0.00015234",
"status": "pending",
"crypto": "BTC",
"rates": "{\"usd\":65670.91,\"eur\":60310.12}",
"created_at": "2026-05-11T14:25:10.000000Z",
"updated_at": "2026-05-11T14:25:10.000000Z"
}
Example Error Responses
Missing API key (401 Unauthorized):
{
"message": "API key not provided"
}
Invalid API key (401 Unauthorized):
{
"message": "Invalid API key"
}
Missing crypto when invoice crypto = ALL (400 Bad Request):
{
"message": "crypto parameter is required for this invoice"
}
Payment already requested (400 Bad Request):
{
"message": "Payment already requested",
"error": "payment.requested"
}