Developers
API Integration
RESTful payment APIs for creating transactions, retrieving status, and managing tokenized references.
Overview
Overview
The BoxCharge API exposes endpoints for payment creation, status retrieval, tokenization, and webhook configuration. All requests use HTTPS and bearer authentication.
Integration
Integration Flow
1. Authenticate
Use a secure bearer key to authenticate requests.
2. Create Payment
Send a payment intent with amount, currency, and method.
3. Handle Response
Process the response and any required next action.
Sample
Request / Response
POST /v1/payments
POST https://api.boxchrge.com/v1/payments
Authorization: Bearer sk_live_***
Content-Type: application/json
{
"amount": 12480,
"currency": "EUR",
"method": "card",
"routing": "smart",
"customer": { "country": "DE" },
"return_url": "https://merchant.com/return",
"webhook_url": "https://merchant.com/hooks/bx"
}
// 200 OK
{
"id": "pay_8f2c...",
"status": "authorized",
"acquirer": "best_available"
}Authentication
All API calls require a bearer token sent in the Authorization header. Production and test keys are isolated.
Security Notes
- • Never expose secret keys in client-side code.
- • Validate webhook signatures before processing.
- • Use HTTPS for all integration endpoints.
Notes
Implementation Notes
- • Use idempotency keys for retried requests.
- • Implement exponential backoff on 5xx responses.
- • Subscribe to webhooks for asynchronous status updates.
FAQ
Developer FAQ
Yes. Sandbox credentials are provided during onboarding and integration coordination.