Docs

Quickstart

1. Sign in at app.micro.broker with login.broker (Google, Apple, GitHub — no passwords).
2. Create a company and register your site or app as a property.
3. Copy the live API key and add the client script to your page.
4. Mark up anything sellable with data-mb-charge.

<script src="https://micro.broker/client.js"></script>
<script>
  microBroker.init({ site: 'thecuriousfold.com', key: 'mb_live_…' });
</script>

Pay button

The button redirects to a site-branded pay sheet on micro.broker. Readers sign in if needed, pick a pool or walled-off wallet, set a cap, pay, and return to your returnUrl with a receipt code.

<script src="/client.js"></script>
<script>microBroker.init({ site: 'thecuriousfold.com' })</script>
<button data-mb-charge="0.14" data-mb-label="Keep reading">Continue</button>

Verifying a payment

The reader comes back with ?mb_receipt=…. That is a claim, not proof — the reader controls their own URL. Exchange it from your server with your API key to learn what was actually paid, and unlock content based on that answer.

curl -X POST https://micro.broker/api/pay/receipt \
  -H "X-Microbroker-Key: mbk_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"code":"mbrc_…"}'

{
  "ok": true,
  "receipt": {
    "transactionId": "…",
    "host": "thecuriousfold.com",
    "amountUnits": 1400,
    "amountEur": 0.14,
    "amountLabel": "€0.14",
    "paidAt": "2026-08-26T10:04:11.000Z",
    "firstRedeemedAt": "2026-08-26T10:04:12.000Z"
  }
}

A code only resolves for the property that earned it, and expires an hour after the charge. firstRedeemedAt tells you whether it had already been exchanged, so you can spot a replayed link.

Webhooks

We POST signed events for every charge, cap change, and payout. Pro plans include 90-day replay from the console.

Event logs

Free plans keep seven days of events. Pro keeps ninety. Every charge, webhook delivery, and dispute action is searchable by property.

Sandbox

Test keys only charge test readers. The console shows a banner until you swap to live keys — the most common support ticket in payment tools.

Security

Hosted on Microsoft Azure. SOC 2 Type II. Reader identities live with login.broker; sites only ever learn that a payment succeeded.

Questions: nb@gyxi.com