Payments

A payment is created server-side with a secret key, then the customer is redirected to a hosted checkout. When the provider confirms, you get a webhook and settlement runs.

Create a payment

curl -X POST https://api.bizzle.my/v1/payments \
  -H "Authorization: Bearer sk_live_yourkey" \
  -H "Idempotency-Key: order-1042" \
  -H "Content-Type: application/json" \
  -d '{"amount": 50000, "currency": "TZS", "description": "Order #1042"}'

Body fields include amount, currency, description, and optional customer / redirect fields. fee and net are computed at creation.

Retrieve and list

• GET /v1/payments/:id — status, fee, net, payout_status.
• GET /v1/payments — list payments.

Confirmations

Inbound provider confirmations arrive on Bizzle’s provider webhooks (not /v1). On confirmation the order is marked paid, settlement runs, and payment.succeeded is emitted to your endpoint.

Note

payment.failed is a registered event. Handle it defensively, but rely on verifying final state via GET /v1/payments/:id.

Refunds

Refunds are available per vertical (for example, event-ticket refunds). Refund actions are writes and accept an Idempotency-Key.

Checkout links

For no-code or embedded checkout, generate a link and share it:

POST /v1/links/new   { store, product, quantity }

The browser SDK wraps this in a one-line <script> button.