Admin panel
Gateways
Install, configure and order the payment gateways your customers can pay with.
Gateways are how your customers pay you. Each one connects Paybob to a payment provider: a card processor, a wallet, a crypto service or a bank transfer. You choose which gateways each Brand offers, and set their limits, fees and discounts.
Packages and gateways
There are two layers:
- A gateway package is the code for one provider, such as Stripe or a mobile wallet. Packages are installed once for the whole installation. Paybob ships with a large set of them, and you can upload more.
- A gateway is a configured copy of a package in a Brand, with your own credentials, name and limits. You can create several gateways from the same package, for example two accounts with the same provider.
Packages work in one of two ways:
- Automatic gateways talk to the provider's API: the customer is sent to the provider to pay, and the provider tells Paybob when the payment is done.
- Manual gateways show the customer where to send money (a wallet number or bank account) and ask for the transaction ID. Paybob verifies it against the payment SMS you received. These need SMS automation set up.
Adding a gateway
Choose a package
Click Create New. A panel lists every installed package, grouped by currency. Search by name or filter by currency, select a package, and click Create.
Configure it
You're taken straight to the new gateway's settings. Fill them in and click Save (see below).
Enable it
New gateways start Inactive, so customers don't see them until they're ready. Set Status to Active on the settings page, or use Enable in the list.
Gateway settings
General Gateway Settings
| Setting | Meaning |
|---|---|
| Display Name | The name customers see at checkout. |
| Minimum Amount | The smallest payment this gateway accepts. |
| Maximum Amount | The largest payment it accepts. 0 means no upper limit. |
| Schedule Start / Schedule End | Optional hours when the gateway is offered, for example 09:00 to 22:00. With only a start, it's available until midnight; with only an end, from midnight. Overnight times such as 22:00 to 06:00 work too. Times follow the timezone in General settings. |
| Fixed Discount / Percentage Discount | Taken off the price when the customer pays with this gateway. |
| Fixed Charge / Percentage Charge | A fee added when the customer pays with this gateway. |
| Status | Active or Inactive. |
Discounts and charges are calculated on the payment amount, and the total is rounded to two decimal places.
Logo
The logo shown at checkout. Each package has a default logo; upload your own (PNG, JPG, WebP or GIF, up to 2 MB) to replace it for this gateway. Remove the upload and save to go back to the default.
Configuration
Everything specific to the provider: API keys, account numbers, mode (live or test) and so on. What's here depends on the package. Secret values such as API keys are stored encrypted. Some packages show read-only values here too, such as the callback URL to register with the provider.
Which gateways a customer sees
At checkout, a gateway is offered only if:
- it's Active;
- the current time is inside its schedule, if it has one;
- the payment amount, converted into the gateway's currency, is between its minimum and maximum;
- Paybob has an exchange rate for the conversion, if one is needed.
Payments in another currency
Each package works in one currency. If a payment is in a different currency, Paybob converts the amount into the gateway's currency with your exchange rates and shows the customer the converted price, including the gateway's fees and discounts. The transaction is saved in the gateway's currency once the customer actually pays.
To group gateways into sections at checkout, such as "Cards", "Wallets" and "Bank transfer", use Checkout Menus.
Manual gateways
Manual gateways, such as personal wallet accounts, are confirmed from the payment SMS your account receives.
Connect it to your SMS
Each manual gateway has a fixed sender ID, usually the package's name, such as bkash-personal. Create an SMS filter with the same Sender ID, the currency the account works in, and the formats of the payment SMS you receive. Until that filter exists, the gateway can't confirm payments. You also need a way for those SMS to reach Paybob: see SMS verification.
Settings
The gateways that come with Paybob share these settings in Configuration:
| Setting | Meaning |
|---|---|
| Numbers (for example bKash Numbers) | The account numbers customers send money to. Add several to spread payments across accounts: each checkout shows one of them, and the same customer always sees the same number for that payment. |
| Verification Method | How Paybob matches the customer's payment to an SMS (see below). |
| Payment Window (Minutes) | For the automatic methods: how long the checkout stays open. The customer sees a countdown, and payments arriving after it aren't matched to that checkout. Default 15. |
| Hold Unmatched Payments | When a customer submits a transaction ID that matches none of your SMS: on, the payment is saved as Pending for you to check; off, the customer is told the transaction wasn't found. |
Verification methods
| Method | How it works |
|---|---|
| Transaction ID (customer submits) | The default. After paying, the customer types the transaction ID from their wallet's confirmation. Paybob looks for a received SMS with that ID and the right amount, and completes the payment at once. |
| Unique Amount (automatic) | Paybob adds between 0.01 and 2.00 to the price, so every open checkout on that gateway has a different amount. The customer pays that exact amount, and Paybob completes the payment when an SMS for it arrives. The extra cents are recorded as a fee. |
| Sender Number (automatic) | Like Unique Amount, and the customer also enters the number they'll pay from. Paybob completes the payment when an SMS arrives from that number for that exact amount. |
With the automatic methods, the customer's page updates by itself every few seconds, and the customer must send the exact amount shown, without rounding. When the payment window runs out, the customer can still enter a transaction ID instead.
In every method, an SMS can only pay one checkout, a transaction ID can only be used once per gateway, and SMS that reached Paybob before the customer opened the checkout are never used. If you've turned on payment tolerance, a rounded amount is accepted with the Transaction ID method only.
Managing gateways
The list shows each gateway's name, package version, currency and status. From a row's menu:
- Configure opens its settings.
- Enable / Disable shows or hides it at checkout. Disabling stops it from being offered for new payments; callbacks for payments already under way are still accepted.
- Delete removes the gateway from this Brand. Its past transactions are kept.
Uploading a package
To add a package that isn't installed, click Upload Gateway and choose its ZIP file (up to 50 MB). The ZIP must contain one folder named after the package, such as my-gateway/. Then use Create New to add it to a Brand.
Uploading a newer version of an installed package updates it in place. Your configured gateways keep their settings. Uploading the same or an older version is refused.
Only install packages you trust
A gateway package runs its own code on your server, with access to your data and your customers' payments. Only upload packages from developers you trust.
To build your own package, see Gateway development.
Permissions
Viewing, creating, updating and deleting gateways, and uploading packages, each have their own permission. Updating a gateway includes its credentials. See Staff and roles.