pay.ifinsta.online staging
One connection carries every payment.
Businesses take payments through their own provider accounts. ifinsta carries the connection; pay keeps the record. Money settles straight into the business's account and never pools anywhere else.
- Settles into the business's own account
- Payers need no account
- One record of what was paid, and of what was refunded
Payments today
Example data| Reference | Amount | Method | Result |
|---|---|---|---|
| SALE-1023 | KES 4,800.00 | Mobile money | Paid |
| SALE-1022 | KES 1,250.00 | Mobile money | Asked the payer to confirm |
| SALE-1021 | KES 95.00 | Cash | Queried the provider |
| SALE-1020 | KES 310.00 | Mobile money | Failed; the payer can try again |
What the engine carries
Every part below is aimed at one job: moving a payment from a payer to a business while proving which one it was.
Checkouts
A checkout is one fixed amount, created over the API from your own systems. Its hosted page asks the payer for nothing more: who is being paid, how much, and the ways it can be paid.
Payment links
A fixed-amount link a business can send in chat or on an invoice. It opens the same sheet a checkout does, and the record says which link led to which payment.
Provider connections
A provider account is connected with one declarative document and the business's own credentials, kept sealed. Connections start on test money, and live money waits until the business and its connections are verified for it.
Webhooks and events
Every state change is delivered as a signed event, retried until acknowledged, and each object's history can be replayed in order. Nothing has to be asked twice.
Refunds
Refund a payment outright, or hand cash back yourself and record it: either way the receipt, the approval and the provider's answer sit on the one record.
Custody by design
pay instructs the merchant's own provider account, learns the outcome, and tells the merchant. It never holds, pools or pays out merchant money, and the schema guard refuses any table that would.
From a reference to a receipt
- A merchant creates a checkout over the API with the amount and a reference, and gets a hosted page to send or embed.
- The payer pays with the method the business's connection offers, on a page that carries the merchant's name and brand.
- pay learns the outcome from the provider's callback and its own status queries, confirms it on the page, and tells the merchant's system with a signed webhook.
Ready to carry payments through your own provider accounts?
The developer guide runs the first payment on test money in minutes.