A workspace of your own
Merchant-scoped payment accounts, orders, credentials and transaction records. Separation is enforced in the database.
A beautiful checkout. Your own payment connections. One thoughtful workspace to keep your business moving.
Start with a sandbox. No money moves in demo mode.
Live processing requires account eligibility and an authorized connection.
From a first payment link to a connected storefront, give your business a consistent payment experience without blending anyone else’s records.
Merchant-scoped payment accounts, orders, credentials and transaction records. Separation is enforced in the database.
Choose your brand color, layout and eligible methods. Provider screens keep their own recognizable identity.
A reference starts a check. Only matching trusted confirmation—or explicitly documented reconciliation—can complete it.
Personal and personal retail account onboarding is supported where the provider permits commercial collection. Entering a number alone never activates live processing.
Explore account eligibility ↗Your server defines the order and price. The customer receives an opaque, expiring checkout link.
Only selected, eligible and available accounts appear. The buyer follows clear provider-specific instructions.
The backend matches receiver, provider, amount, transaction reference and payment window. Unconfirmed stays pending.
A modular provider catalog with recognizable branding. Catalog availability is separate from live processing approval.
Logos identify their respective providers; they do not indicate endorsement or partnership. International methods require an eligible merchant and approved hosted adapter.
Use a hosted link, redirect or secure modal. Your backend creates the session and verifies the final result before fulfilling the order.
Read the documentation ↗Planning rates for Ekannto Pay software. Provider costs, FX, taxes and disputes are separate and contract-specific. Subscription sales are not active in this pilot.
Illustrative software fee per confirmed BDT payment.
Planning example, USD only. Approved partner integration required.
Separate usage-fee invoices are included. Subscription purchasing and commercial plans remain in the implementation backlog.
View all fee rules ↗You can register it for eligibility review or sandbox use. Live commercial collection is available only if the provider permits that category and the connection has been approved. A Personal Retail Account may be appropriate for eligible small businesses.
No. The reference is a lookup input. The actual receiver, provider, amount, timing and evidence must match. Unknown or mismatched receipts remain pending.
To the merchant’s own receiving account. This pilot does not hold funds, maintain a spendable wallet or perform automatic payouts.
Supabase authentication and Expo mobile source are included. Google requires the project’s OAuth configuration; native installation and store publication require signed builds and developer accounts.