KDC Pay Sign in

Payment-gateway orchestration for India

One routing layer in front of your own payment gateways.

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

KDC Pay Policy: your order

Back to youOne payment

The payment goes to gateway 1, first in your order.

An illustration, not live data.

Bring your own gateways

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.

  • Your accounts

    Connect the gateway accounts you already hold, as many as you have.

  • Your pricing

    You pay each gateway what you agreed with it. The fee a gateway reports is booked in your ledger.

  • Your settlement

    Money settles from the gateway straight to your bank.

Gateways today
PaySharp for UPI intent, QR and collect.
Zoho Payments for payment links, in-person terminals and UPI AutoPay.

Routing per payment method

Each method gets its own policy: an ordered list of your gateways and a strategy. Methods without one follow your default policy.

  • UPI intentupi_intent
  • UPI QRupi_qr
  • UPI collectupi_collect
  • Payment linkpayment_link
  • In personin_person
  • UPI AutoPayupi_autopay

Strategy

Your priority order

Gateways are tried in the order you set. Nothing changes unless you change it or a gateway goes down.

Strategy

Best recent success rate

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.

When a gateway goes down

Every gateway has a circuit breaker for each payment method. A gateway that keeps failing is skipped until it recovers.

  1. 3 failures in a row

    Timeouts, network or server errors, throttling or rejected credentials on create calls. A gateway declining one payment does not count.

  2. Rests for 60 s

    Payments skip it. Each time it trips again the rest doubles, up to 15 minutes.

  3. Tried again

    One success closes the breaker. One more failure rests it again.

  4. Back in rotation

    It takes payments in its usual place in your policy.

Switching inside the request

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.

Where it holds back

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.

Collect anywhere

The same routing order and the same ledger sit behind every way a payer can reach you.

  • Inside WhatsApp

    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.

  • Short links on kdc.pe

    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.

  • UPI AutoPay

    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.

  • Documents

    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 ledger

One set of books for your business, whichever gateway a payment went through.

  • Double entry, integer paise. Every amount in the books is a whole number of paise.
  • Append-only, enforced by the database. Every transaction must balance when it commits. Entries cannot be edited or deleted.
  • Checkable. An integrity endpoint recomputes the trial balance and matches postings against payments, refunds and settlements.
  • Statements. Opening and closing balances for any date range, in JSON or CSV.
  • Corrections. A wrong entry is never changed. It is reversed by a new transaction, so the history stays whole.
A captured payment of ₹499.00
AccountDebitCredit
Gateway clearing493.10
Gateway fees5.00
GST on fees0.90
Sales499.00
Total499.00499.00
Example figures. The fee and GST are whatever your gateway reports.

For developers

A JSON API at api.kdcpay.com/v1. Bearer auth, amounts in paise, and an Idempotency-Key on payments and refunds.

Create a payment
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"}'
  • Idempotency

    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.

  • Signed webhooks

    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.

  • Routed by default

    Leave out route and the payment follows your policy for its method. Send one and it is pinned to that gateway.

  • API keys

    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.

Security

What the system does, stated plainly.

Merchant isolation
Enforced in the database by PostgreSQL row-level security, not only by application code.
Stored credentials
Gateway credentials, WhatsApp tokens and webhook secrets are encrypted with AES-256-GCM, each bound to its own row. The API only ever returns a masked hint.
Passwords and keys
Passwords are hashed with scrypt. Session tokens and API keys are stored only as SHA-256 hashes.
Incoming webhooks
Signatures are compared in constant time. Where a gateway does not sign its webhooks, the webhook is only a hint: KDC Pay asks the gateway itself for the amount and status.
Outgoing requests
Calls to gateways and to your webhook URL pass an egress guard: HTTPS only, no private or local addresses, no redirects followed.
Audit
The audit log is append-only and hash-chained per merchant. One API call recomputes the chain.

Your gateways. One place to run them.

Accounts are opened by the KDC Pay team. If you have one, sign in to the dashboard.