End-to-End Integration
You expose two REST endpoints on your server. Kuickpay calls them automatically whenever a consumer pays through any channel — bank app, ATM, or mobile wallet. No SDK required; just standard HTTP JSON.
username and password headers you provide to Kuickpay during onboarding.What happens at payment time
Consumer opens their bank app, visits an ATM, or uses the Kuickpay app. They enter their consumer number.
Kuickpay sends a POST request with the consumer number and bank identifier. Your API looks up the account.
Your API responds with amount, due date, bill status, and consumer name. Kuickpay shows this to the consumer.
Consumer reviews the bill and confirms. Payment is processed by the bank or channel.
Kuickpay sends the transaction ID, amount paid, and channel details. Your API must record the payment.
Your API marks the bill as paid, generates a receipt ID, and returns it. Consumer receives payment confirmation.
Your integration steps
Understand exactly what request Kuickpay sends and what response your APIs must return.
Implement the two POST endpoints on your server. Share the URLs, username, and password with the Kuickpay team to get your Institution ID.
Enter your Institution ID and endpoint details. Your profile is fetched and your setup is validated for UAT.
Simulate a complete Bill Inquiry → Bill Payment flow against the sandbox. See exact request/response payloads.