Accept payments
QR, receive links, and account names for hotels, restaurants, and markets. Customers pay in Sika; you never hold their keys.
For businesses & builders
Integrate Sika App. Keep custody with the customer.
Banks, marketplaces, hotels, and restaurants can accept or request payments through documented deep links and a mint API — without ever handling private keys. Access is reviewed; credentials are not self-serve.
Integration patterns
Request via API
Your backend mints a short-lived pay intent. Send the link on WhatsApp, SMS, or email — the customer signs in their wallet.
Open wallet to sign
Deep-link or WharfKit session for advanced apps and banks. The user always confirms the transfer.
Fee schedule
Person-to-person stays free of platform fees. Commerce rails use a clear list price — volume and banks negotiate after review.
| Rail | Platform fee |
|---|---|
| P2P (wallet → wallet) | 0% |
| Commerce list (QR, pay link, API) | 1.5% (merchant-absorbed) |
| Pilot / intro | 1.0% (approved, time-boxed) |
| Volume / contracted | 0.8–1.2% |
| Strategic banks / large chains | 0.5–0.8% |
Example at 1.5%: customer pays GHS 100 → merchant receives GHS 98.50 → Sika App fee GHS 1.50.
Getting started
- Request access — tell us your business type, country, and volume band. We review and issue a
merchantId+ mint secret for your server. - Pick a path — accept (QR / receive), request via API (
POST /api/v0/pay/intent), or open-wallet sign for advanced apps. - Mint on the server only — never put secrets in a browser or mobile app. Send the returned
hrefto your customer. - Customer signs in Sika App — they see amount and fee lines before confirming. You reconcile on-chain.
POST /api/v0/pay/intent
Authorization: Bearer <mint_secret>
{
"to": "hotel.acc",
"amount": "100.00",
"memo": "Room 214",
"merchantId": "merchant_hotel_accra"
}Documentation
Engineer copies also live in the repository under docs/partners/ and sdk/. We publish integration contracts — not internal identity, settlement, or unpublished product IP.