Developers

Charge from your own site.

One call creates the charge, one webhook tells you it is paid. Your customer pays from the mobile money they already have, and it lands in yours.

Test keys work before you are verified. No sandbox to set up.

Keys

What happens when it leaks.

Keys live on web servers, and web servers end up in git history, log aggregators and screenshots. So the question is not whether one gets out. A Flash key can ask for money and see whether it arrived. That is the whole list.

It can ask for money

Create a charge, and read whether it has been paid. Both of those pay you.

It cannot take any

No payouts, no refunds, no moving money out of the account. Those need you, signed in.

It cannot breed

A key cannot mint another key, read your customers, or change your account. Revoke it on its own, instantly.

Stored as a SHA-256 hash and shown once, at creation. Prefixed flash_live_ and flash_test_ so a key is recognisable on sight — in a log, a diff, or a secret scanner.

The integration

Three steps, and you are done.

1Create the charge

Send the amount and where to tell you. You get back a link to send them to.

curl -X POST https://api.joinflash.xyz/api/transactions/payment-links/ \
  -H "Authorization: Bearer flash_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 450,
    "description": "Order 1041",
    "callback_url": "https://yourshop.co.zm/flash/webhook",
    "return_url": "https://yourshop.co.zm/thanks"
  }'
{
  "link_code": "k3mq8v",
  "url": "https://app.joinflash.xyz/pay/k3mq8v",
  "amount": 450.0,
  "description": "Order 1041",
  "is_active": true,
  "use_count": 0,
  "expires_at": null,
  "callback_url": "https://yourshop.co.zm/flash/webhook",
  "return_url": "https://yourshop.co.zm/thanks"
}

Leave amount out for an open link and the payer enters it.

2Send them to it

Redirect to url, or show it as a QR. Your customer needs no app and no Flash account — they approve it on their own phone, with their own mobile money PIN. When they are finished they land on your return_url.

3Get told it is paid

Flash POSTs to your callback_url the moment the carrier confirms it. Retried if your server is down, so deduplicate on event_id — it is stable per payment.

POST https://yourshop.co.zm/flash/webhook
X-Flash-Signature:  v1=9f2c…
X-Flash-Timestamp:  1792143600
X-Flash-Event-Id:   8c1d7e40-…

{
  "event": "payment.succeeded",
  "event_id": "8c1d7e40-…",
  "link_code": "k3mq8v",
  "amount": "450.00",
  "currency": "ZMW",
  "reference": "FL-8841029",
  "description": "Order 1041",
  "invoice_id": null,
  "paid_at": "2026-10-22T14:07:31+02:00"
}

Polling instead? GET /api/transactions/pay/{link_code}/ returns the same link with use_count and payable. The webhook is better; this is for reconciling.

Webhooks

Check the signature before you ship anything.

An unsigned webhook saying “order 1041 is paid” is an instruction anyone on the internet can send. Every delivery carries an HMAC-SHA256 over the exact bytes of the body, keyed on a secret only you and Flash hold, with the timestamp inside the signed material so a captured call cannot be replayed next week.

import hmac, hashlib, time

def verify(body: bytes, timestamp: str, signature: str, secret: str) -> bool:
    if abs(time.time() - float(timestamp)) > 300:
        return False
    expected = "v1=" + hmac.new(
        secret.encode(), timestamp.encode() + b"." + body, hashlib.sha256
    ).hexdigest()
    return hmac.compare_digest(expected, signature)

Your signing secret is in your Flash account, next to your keys. It is yours alone — it cannot verify another shop’s webhooks, and theirs cannot forge yours. Verify against the raw body, before parsing it.