GET /v1/merchant
Read merchant, network and processing-credit information.
DEVELOPERS
Create payments. Reconcile receipts.
Use network-specific API credentials on your server. Start with testnet and handle retries before accepting real funds.
ONE CONNECTED WORKFLOW · ILLUSTRATION
Signed updates, connected end to end.
One payment. A clear trail of updates.
FIRST REQUEST
Read your merchant configuration.
curl https://brislet.31-97-62-74.plesk.page/v1/merchant \
-H "Authorization: Bearer $BRISLET_API_KEY"Use your own server-side key. Never put an API credential in browser code.
API SURFACE
Core integration endpoints.
GET /v1/connector
Check connector scopes and readiness.
POST /v1/payments
Create a request with invoice_reference, currency and amount. Supply an Idempotency-Key for retries.
GET /v1/payments/{id}
Retrieve the current payment state.
POST /v1/webhook
Configure your callback URL and signing secret.
DELIVERY AND RECOVERY
Treat updates as repeatable.
Authenticate
Validate callback signatures and match the expected merchant, network and payment reference.
Retry safely
Reuse the original operation identity after a timeout. Do not create a second payment request for the same retry.
Reconcile
Record a durable native receipt reference. A repeated callback must not add a second invoice payment.
DOCUMENTATION
Read the setup guide