Console →
How it works

A single hop from your app to settlement.

Your business never talks to the gateway directly. It talks to Rythzen Pay, and Rythzen Pay does the rest.

STEP 01

Create a charge

Your backend POSTs the order amount and customer details to the Rythzen Pay API with your brand’s key pair. You get back a hosted checkout URL.

STEP 02

Customer pays

We redirect the customer to a secure checkout to pay with a card or wallet. Their payment details are handled by the certified gateway — never by your servers or ours.

STEP 03

We verify the outcome

When the customer returns, Rythzen Pay re-checks the result server-to-server with the gateway. The ?r=success hint from the browser is never trusted on its own.

STEP 04

You get notified

We fire a signed webhook to your backend and bounce the customer back to your return URL with a signed status. The transaction is written to the central ledger, tagged to your concern.

Because the gateway only ever sees one merchant and one callback domain (payments.rythzen.com), every Rythzen brand shares a single, clean merchant relationship. You onboard businesses on your side, not the gateway’s.

The money math

By default the gateway’s service charge is grossed-up onto the amount the customer pays, so the merchant nets exactly the price it set. This is configurable per concern — you can also absorb the fee instead.

Who pays the gateway fee is set per concern in the Rythzen Pay console, not in your request. Choose customer pays (the price is grossed-up so you net exactly what you asked for), you absorb it, or a split. Your integration always sends the amount you want to NET and reads amount_gross from the response to show the customer. pass_fee_to_customer is now an optional override that is ignored unless the concern explicitly allows it.
Price you set
৳1,000.00  (what your brand nets)
Gateway fee (example 2.5%)
৳25.64
Customer is charged
৳1,025.64
Settled to merchant
৳1,000.00