Strategy
Your priority order
Gateways are tried in the order you set. Nothing changes unless you change it or a gateway goes down.
Payment-gateway orchestration for India
You keep your gateway accounts, your pricing and your settlements. KDC Pay sends each payment to the gateway that suits it, and to the next one when that gateway is down.
One API, one dashboard, one ledger.
Payment in₹499 · UPI intent
Back to youOne payment
The payment goes to gateway 1, first in your order.
Every gateway behind KDC Pay is one you signed up for yourself. KDC Pay sits in front of them and decides which one takes each payment.
Connect the gateway accounts you already hold, as many as you have.
You pay each gateway what you agreed with it. The fee a gateway reports is booked in your ledger.
Money settles from the gateway straight to your bank.
Each method gets its own policy: an ordered list of your gateways and a strategy. Methods without one follow your default policy.
upi_intentupi_qrupi_collectpayment_linkin_personupi_autopayStrategy
Gateways are tried in the order you set. Nothing changes unless you change it or a gateway goes down.
Strategy
The gateway whose payments of that method ended best over the last 24 hours goes first. Rates within 2 points count as a tie, and your order settles it.
The dashboard's Routing screen shows, per method, the order the next payment would try your gateways in, with each one's health and success rate. A payment can also be pinned to one gateway through the API.
Every gateway has a circuit breaker for each payment method. A gateway that keeps failing is skipped until it recovers.
Timeouts, network or server errors, throttling or rejected credentials on create calls. A gateway declining one payment does not count.
Payments skip it. Each time it trips again the rest doubles, up to 15 minutes.
One success closes the breaker. One more failure rests it again.
It takes payments in its usual place in your policy.
If the chosen gateway has an outage while a payment is being created, the same payment moves to the next gateway: same id, same reference, same Idempotency-Key. Your API call still returns one working payment.
When the first gateway's answer is unknown, a payment moves only for UPI intent, QR and payment links. A collect request or a terminal push may already be in front of the payer, so it stays put. Mandates and WhatsApp orders follow your routing order but do not switch inside the request. If every gateway is down, the payment is still attempted.
The same routing order and the same ledger sit behind every way a payer can reach you.
Send an order as a WhatsApp message with a UPI payment attached, through your own gateway. When the gateway confirms the payment, the order status in the chat is updated.
Every payment, issued quote or invoice, and mandate gets a payer page at kdc.pe/<code>, one URL from quotation to receipt, in English and Hindi. Reusable pay links work the same way.
Mandates on gateways that support them, with pre-debit notification. Recurring schedules create each cycle's debit, and each debit is sent to the gateway at most once.
Quotes, GST invoices with CGST, SGST and IGST per line, credit notes, and a receipt for every successful payment and refund. Numbering is gapless per fiscal year. HTML and PDF.
One set of books for your business, whichever gateway a payment went through.
| Account | Debit | Credit |
|---|---|---|
| Gateway clearing | 493.10 | |
| Gateway fees | 5.00 | |
| GST on fees | 0.90 | |
| Sales | 499.00 | |
| Total | 499.00 | 499.00 |
A JSON API at api.kdcpay.com/v1. Bearer auth, amounts in paise, and an Idempotency-Key on payments and refunds.
curl -s https://api.kdcpay.com/v1/payments \
-H "authorization: Bearer $TOKEN" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: order-1001' \
-d '{"amount_paise": 49900, "method": "upi_intent"}'
Repeat a payment or refund request with the same Idempotency-Key and you get the original back. Reuse the key with a different body and you get a 409.
Once you generate a webhook secret in Settings, every webhook KDC Pay sends you carries x-kdcpe-signature: a timestamp and an HMAC-SHA256 of the timestamp and body, made with your secret.
Leave out route and the payment follows your policy for its method. Send one and it is pinned to that gateway.
A key is shown once and stored only as a hash. Keys are created and revoked from a signed-in session, and record who created them.
What the system does, stated plainly.
Accounts are opened by the KDC Pay team. If you have one, sign in to the dashboard.