Skip to main content
Complete these before accepting payments. Dashboard → Settings. Click Save Changes when done.

Business

Payout

Currency determines which payout methods are available.

M-Pesa mobile (KES)

Phone number (07XXXXXXXX) + network (Safaricom).

Buy Goods till (KES)

Your till number. Settlements show as customer payments in your till statement.

Paybill (KES)

Paybill number + account number. Both required.

Bank Transfer (KES, NGN, GHS, UGX)

Account number, bank code, bank name. Account Name must match the bank record exactly — mismatches cause failed disbursements.

Mobile Money (GHS, UGX)

Phone number + network (MTN, Airtel, etc.).
Account Name is required for all methods. It must match the name on your bank, M-Pesa, or mobile money account.

Settlement mode

Pick how payments settle by default. Local currency converts automatically and pays out to M-Pesa, mobile money, or your bank, same as always. USDC skips that step, costs less, and leaves the deposit sitting in your wallet. This sets the default for new sessions. You can also override it per session from checkout sessions instead. Once a session is created its mode is locked in, so changing this setting later won’t touch anything already in progress.

Destination chain

If you’re settling in USDC, pick which chain your payments land on: Base, Arbitrum, Avalanche, Optimism, Ethereum, or Polygon. Base needs nothing extra, since that’s where the deposit already sits. Any other chain gets forwarded there automatically after each payment, and you cover a small bridge fee out of the amount. Switching chains only changes where the next payment lands, not USDC you’re already holding. Your wallet shows a separate balance for every chain you’ve received on. Set a unique slug → get a shareable URL:
Slugs are unique across Minisend. If yours is taken, try a variation.

Webhooks

Webhook configuration used to live here as one section among several. It has its own screen now, Dashboard → Webhooks, since the real feature outgrew a single URL field: every event Minisend has ever tried to send you, and a way to fix it when one didn’t land.

Endpoint

Paste your HTTPS URL, something like https://yourbusiness.com/webhooks/minisend, and save. Minisend starts posting signed events to it right away. Leave it blank and you get no server-side notifications at all, so you’d poll the status endpoint instead, which works but means your code has to keep asking rather than being told.

Secret

Generated automatically the first time you land on that page, shown once, in a copy-once banner exactly like an API key. Copy it immediately and store it wherever your server reads its webhook configuration from. Click Regenerate to rotate it. That invalidates the old value straight away, every signature Minisend computes afterward uses the new one, so update your server first or right after, not sometime later.
See Webhooks for signature verification and the full event list.

Test, deliveries, and replay

A Send test button fires a signed sample payload at your endpoint on demand, so you can confirm your signature check works before a real payment depends on it. Below it, every delivery Minisend has actually attempted is listed, newest first, with its status and response. If one failed and you’ve since fixed your endpoint, replay sends it again rather than waiting out the retry schedule.
Five failed deliveries in a row and that screen flags your endpoint as down. Fix it, then replay what was missed.

Saving

Click Save Changes (or Create Account if new). Required fields are marked with *.