Skip to main content
​
CheckoutPayment links
Charge a customer without writing a line of frontend. Create a payment link (a single-use charge for one customer) or a payment page (a reusable URL anyone can pay) from the dashboard or API, send the URL, and your customer pays on a hosted checkout that accepts mobile money, bank transfer, and stablecoins on one page.
  • Hosted page handles the full lifecycle: provider selection, phone prompts, dedicated virtual account numbers, crypto addresses with QR codes and locked FX rates, live status, partial payments.
  • Open-amount pages let the payer choose what to pay — donations, top-ups, pay-what-you-want.
  • Merchant branding: your name, logo, and accent color.
  • Every attempt is a checkout session you can inspect in the dashboard.
​
DashboardAPI

​
Request logs

Every request to your workspace — by API key or team member — is now logged and browsable under Developers → Request logs: method, endpoint, status, duration, IP, and the redacted request body. Failed auth attempts are captured too. Look up any request by the x-request-id from its response header.
​
APIFX

​
Live FX rates

Cross-currency payouts and conversions now price from live market rates rather than a static table. GET /v1/rates/{origin}/{destination} returns the current all-in rate — the same one applied at execution.
​
APIWebhooks

​
Webhooks, end to end

Signed webhooks for every money event — payout.completed, payout.failed, collection.*, order.*, conversion.completed, account.credited, and more. Manage endpoints in the dashboard, verify with your signing secret, and replay any delivery. Failed deliveries retry with backoff for about a day, and consistently failing endpoints auto-disable instead of silently rotting.
​
APIOrders

​
Orders: cross-rail pass-throughs

One call that collects on one rail and pays out on another — for example, accept USDC on Solana and deliver Ghanaian cedis to a mobile money wallet. POST /v1/orders with a from and a to; the order carries a merged timeline across both legs, and the dashboard shows every order with status, origin, and destination filters.
​
DashboardCollections

​
Collections: three views, one ledger

Inflows, virtual accounts, and crypto addresses each get a dedicated dashboard view over the same underlying table — filter collections by the virtual account or crypto address that received them.
​
DashboardAPI keys

​
API keys: scopes, spend caps, IP allowlists

Full key management in the dashboard: create with scoped permissions, restrict by caller IP, and set daily / per-transaction / monthly USD spend caps enforced across all currencies. Keys are shown once and stored hashed.