Choosing a payment gateway for eSIMs
The gateway decides more than your fees: it decides whether you launch on time, what your customer sees on their statement, and who pays for a disputed charge.
هذه المقالة منشورة بالإنجليزية. الموقع العربي مترجم بالكامل، أما المدونة فلا — لأن ادعاءً واحداً مترجماً ترجمة سيئة عن تسعير منافس أسوأ من عدم وجوده.
The decision that blocks the launch
Of everything involved in opening an eSIM store, the payment gateway has the longest lead time and the least flexibility. The storefront can be live in a day. A merchant account can take a fortnight, can be refused, and cannot be worked around.
It is also the component that decides the most about your business afterwards. Whose name is on the money, what your customer sees on their statement, who eats a disputed charge, and how much of a five-dollar sale survives to your balance are all gateway questions, not storefront questions.
Start the gateway application before you choose a platform, not after. Everything else on the launch checklist can be done while you wait; nothing can be done without this.
Where the money actually goes
Card pricing is usually quoted as a percentage plus a fixed amount per transaction. For most e-commerce the percentage is the part worth negotiating. For eSIMs it is the other way round.
The fixed fee is the one that hurts
A fixed per-transaction fee of around thirty cents is trivial on a hundred-dollar order and brutal on a five-dollar one, where it is roughly six percent of the entire sale before the percentage rate is even applied. Small eSIM packages are the worst-case basket for card pricing, which is an argument for bundles and multi-eSIM carts rather than for cheaper packages.
Three costs that do not appear on the rate card
- Currency conversion. If you price in one currency and settle in another, someone takes a spread. Check whether it is the gateway, your bank, or both.
- Cross-border and card-type surcharges. Your buyer is a traveller, so a high share of your volume is foreign-issued cards, which frequently carry a higher rate than the headline one.
- Payout delay and rolling reserves. A new merchant in a category a processor considers risky may face a holdback on a share of receipts, which is a cash-flow problem rather than a cost.
None of these is a reason to avoid card payments. They are reasons to read the offer rather than the headline rate, and to measure your effective rate from a real statement after your first month.
Getting approved, and why you might not be
Selling prepaid connectivity to travellers touches several things underwriters look at closely: digital goods with instant delivery, an international customer base, low average order values and a young business. That combination is not disqualifying, but it does get read carefully.
What helps, and costs you nothing to prepare in advance:
- Register the business entity first and have its documents ready. Most processors will not open a merchant account for an individual.
- Have a live site — even a pre-launch one — with your terms of sale, refund policy and contact details published. Underwriters open the site.
- Describe the product plainly in the application: prepaid mobile data for travellers, delivered as a QR code, activated by the customer. Vagueness here creates questions.
- Say what your expected volume and average order value are, and keep the number honest. An estimate that turns out wrong by an order of magnitude triggers a review.
- Have a second processor application in progress, or at least identified. A single point of failure on payments is a single point of failure on revenue.
If a processor declines you, ask what category they placed you in. Sometimes the answer is a miscategorisation you can correct rather than a judgement about your business.
Chargebacks, and the digital-goods problem
A chargeback is a customer disputing a charge with their card issuer rather than with you. You lose the sale, usually pay a fee on top, and if enough of them accumulate you can lose the merchant account itself. For a product delivered instantly and consumed abroad, the odds are stacked awkwardly.
Why eSIMs attract them
- The buyer does not recognise the charge. This is the single most common cause of a dispute across all of e-commerce, and it is entirely preventable — see below.
- The eSIM did not work for them. Often a device or activation problem rather than a faulty product, but the customer experienced a failure and was abroad when it happened.
- There is no delivery to prove. You cannot show a signed courier receipt for a QR code, so your evidence has to be built differently.
What actually reduces them
- A statement descriptor the customer recognises. If your store is called one thing and the descriptor says another, you are generating disputes on purpose. This is only in your control if the payment account is yours.
- Strong customer authentication where it applies. A card authenticated by the issuer shifts liability for fraudulent-use disputes away from you in most schemes — check how your gateway handles it rather than assuming.
- Keeping delivery evidence. Timestamped records of when the QR was issued, when it was delivered, and — if your provider exposes it — when the profile was installed and data was used. Usage data is the strongest evidence a digital seller has.
- Answering fast. A large share of disputes start as a support message that went unanswered. A refund you issue costs you the sale; a chargeback costs you the sale plus a fee plus a mark on your ratio.
That last point is the one worth internalising. Refunding a marginal case quickly is almost always cheaper than winning the dispute a month later.
Choosing between them
Once approval is plausible, the comparison is narrower than the marketing suggests. Six questions separate real options.
| Question | Why it matters for eSIMs specifically |
|---|---|
| What is the fixed per-transaction fee? | It dominates small baskets. The percentage barely matters at $5. |
| Whose name is the merchant account in? | It decides the descriptor, the cash flow and who owns the customer. |
| Which currencies can you settle in? | A traveller audience pays in many; conversion spread is a silent cost. |
| How are foreign-issued cards priced? | Most of your volume will be foreign-issued. |
| What is the payout schedule and any reserve? | You pay providers up front and get paid later — that gap is working capital. |
| Can the platform you chose connect it? | A gateway your storefront cannot integrate is not an option, however good. |
The second row is the one people skip and later regret. A platform that takes payments into its own account and forwards you a balance is a fundamentally different business relationship from one where the merchant account is yours — the difference shows up on the statement descriptor, in a dispute, and on the day you want to leave.
Esimbit is built on the second arrangement: you connect your own payment account and customer money never passes through us. That is not automatically the right answer for everyone, but it is the answer that decides the other five rows for you.
الأسئلة الشائعة
What payment gateway is best for an eSIM store?
There is no universal answer, because approval, pricing and settlement currencies all vary by country and entity. The comparison that matters for eSIMs is the fixed per-transaction fee rather than the percentage, whose name the merchant account is in, how foreign-issued cards are priced, and whether the platform you have chosen can connect it.
Why do card fees hurt eSIM sales so much?
Because the fee has a fixed component — commonly around thirty cents — and eSIM baskets are small. On a five-dollar package that fixed part alone is roughly six percent of the sale, before the percentage rate applies. It is the strongest argument for bundles and larger packages rather than cheaper ones.
Will a payment processor approve an eSIM reseller?
Usually, though the combination of digital goods, instant delivery, international customers and low order values gets read carefully. A registered entity, a live site with published terms and a refund policy, and a plain description of the product make approval materially more likely.
How do I fight a chargeback on an eSIM?
You cannot produce a delivery signature, so build the evidence differently: timestamped records of when the QR was issued and delivered, and where your provider exposes it, activation and data-usage records. Usage data is the strongest evidence available to a digital seller. Preventing disputes with a recognisable statement descriptor and fast replies works better than winning them.
Should customer payments go to my account or the platform’s?
Yours, if you want the customer relationship. The account holder controls the statement descriptor, receives the money directly, and keeps a customer record independent of the platform. If payments land in the platform’s account, the descriptor is theirs, the cash flow is theirs, and leaving is harder.