Payment gateways and how a payment is verified
Take cards and wallets online through SSLCommerz, bKash, Nagad, Paystation or EPS. Jukto never trusts the browser return: it asks the provider itself.
A gateway lets buyers pay online on the provider's hosted page. When the buyer comes back to your store, the browser return proves nothing. Jukto asks the provider's server whether the money really arrived, and only then marks the order paid.
The gateways#
| Gateway | Notes |
|---|---|
| SSLCommerz | Cards, mobile banking and internet banking on its page. Supports a refund call |
| bKash | Buyer pays from the bKash wallet. Supports a refund call |
| Nagad | Wallet payments; Nagad whitelists your store address for live payments |
| Paystation | One connection for cards and wallets; sends no signature, so Jukto always asks Paystation |
| EPS | Cards and mobile wallets; register your store address as the merchant domain |
How a payment is verified#
Text version of the diagram
- Buyer pays on the gateway page to Returns to your store
- Returns to your store to Jukto asks the gateway directly
- Gateway notification (IPN) to Jukto asks the gateway directly (Second path)
- What does the gateway say? to Order marked paid (Paid)
- What does the gateway say? to Still waiting (Pending)
- What does the gateway say? to Payment failed (Failed)
- Jukto asks the gateway directly to What does the gateway say?
- Still waiting to Background check
- Background check to Jukto asks the gateway directly (Ask again)
- Background check to Order cancelled, stock released (Never paid)
- Return. The page the buyer lands on only tells Jukto when to ask. Nothing in the address counts as proof.
- Notification (IPN). The gateway can also call Jukto's address. That call is a second trigger; the answer still comes from asking the provider.
- Background check. About every five minutes a job looks for orders still waiting for their online payment. It asks the provider one last time, because a late payment wins; if the order is still unpaid after the waiting time, it is cancelled and its stock goes back on sale. If the money may be held at the provider, the order is flagged for review instead of cancelled.
- Safe to repeat. A payment already recorded as paid is never booked twice, even if the return, the notification and the job all arrive together.
Connect a gateway#
- 1
Open Tools > Integrations > Payments
Choose the gateway.
- 2
Enter the keys from the provider's merchant portal
Each mode has its own keys. Find the API or credentials section of your provider dashboard. Keys are stored securely and never shown again.
- 3
Choose Sandbox or Live
Use Sandbox to try it first. Keep every key of one mode together; mixing modes fails.
- 4
Register addresses only where the provider asks
The page shows your Notification (IPN) address and Your store address with a Copy button. Jukto sends the buyer back by itself, so nothing needs registering for the return.
- 5
Run Test connection, then switch it on
Make a small test order before you rely on it.
Check a payment yourself#
The gateway page lists every attempt in Payments: the order, the status (Started, Waiting, Paid, Failed, Cancelled, Refunded), the mode, the fee and a reference. Press Check again to ask the provider now. The answer is one of: paid, already paid, still waiting, failed, cancelled, refunded, no answer from the provider, or "amount does not match, check the provider panel".
Common problems#
The buyer paid but the order is still To confirm.
Open the gateway page and press Check again on that payment. If the provider says paid, the order updates. If the provider says "no answer", check the keys and the mode.
The order was cancelled and the money still arrived.
The order shows that a late payment arrived. Refund it with Refund online, or in the provider panel. See Returns and refunds.
Where are the exact steps for one provider?
See the provider guides under Integrations, for example Payment integrations.
Comments (0)
Anyone can comment. Please do not post phone numbers, passwords or customer details.