Wallet Auto Credit

Collect Payment. Credit the Wallet. Keep Sending.

SMS aggregators and white-label resellers should not wait on a manual recharge ticket every time a customer buys credits. SMPP Center wires the payment gateway you already use, then posts wallet or SMS credits automatically once that gateway confirms the payment, using the pack, tax, and bonus rules configured in the system.

This is not a locked merchant. Razorpay in India, Stripe in the US and EU, Paystack in Kenya, or a processor in the UAE can all sit in front of the same credit engine. See SMS and SMPP Software Features for the panels those credits are spent in.

13 years running production SMS traffic, including online recharge for reseller networks.

Dark theme illustration of a digital wallet receiving credits after an online payment

How Auto Credit Works

Credits move only after the gateway says the money is good. Configuration, not a spreadsheet, decides how many credits land in the wallet.

Diagram of user payment, gateway confirmation, webhook verify, auto wallet credit, then sending SMS

User chooses a pack

Downline users pick a credit pack, currency, and tax-inclusive price from the panel you configured.

Gateway checkout

UPI, cards, net banking, or wallets open on the merchant account belonging to Admin or that reseller.

Webhook confirm

The callback is signature-checked. Pending or failed payments never touch the wallet.

Auto credit

Credits, bonus, and GST handling post exactly as configured. Every recharge is logged.

Spend on channels

The same wallet pays SMS, WhatsApp, RCS, or voice according to your rate cards.

Popular Payment Gateways We Wire

Start with a well-known processor in your market, or bring the one your finance team already settled. The credit rules stay inside SMPP Center.

India

Razorpay, PayU, CCAvenue, Paytm, Cashfree, PhonePe, Instamojo. UPI, cards, net banking, and wallets.

US, UK, EU

Stripe, PayPal, Braintree, Authorize.net, Adyen, Mollie, 2Checkout. Cards and local methods the processor supports.

Africa and GCC

Paystack, Flutterwave, and regional processors used by aggregators in Kenya, South Africa, Nigeria, and the UAE.

Any other gateway

If it offers a checkout URL plus a signed webhook or IPN, we can map it to the same auto-credit engine.

Dark theme illustration of a reseller dashboard connecting payment checkout to rising wallet credits

White-Label Resellers Use Their Own Credentials

A reseller on your SMPP platform should collect as themselves, not as you. They paste their Razorpay, Stripe, PayU, or PayPal keys into their own panel, publish credit packs to downline users, and start accepting payment the same day.

  • Each reseller merchant account is isolated. Settlement hits their bank, not the platform wallet.
  • Downline users see the reseller checkout branding, then receive credits on that reseller account.
  • Admin can still run a master gateway for direct users while resellers run theirs in parallel.
  • Pack price, bonus credits, and tax follow the reseller rate card you already configured.

This sits next to white-label tools such as the Excel SMS Plugin and SMS Gateway Software for Resellers.

What the System Configures Before Credit Posts

Setting What it controls
Credit packs How many SMS, WhatsApp, RCS, or mixed credits a successful payment adds, including optional bonus credits.
Pricing and tax Display price, GST or VAT treatment, and currency shown at checkout for that Admin or reseller.
Gateway keys Merchant ID, API key, webhook secret. Stored per Admin or per reseller, never shared across tenants.
Success rule Only gateway-confirmed success credits the wallet. Pending, failed, or duplicate callbacks are ignored or logged.
Audit trail Payment reference, amount, pack, and credited balance are written to credit-usage logs for reconciling with the gateway dashboard.

Need Razorpay, Stripe, or a custom gateway on your SMS panel?

Tell us the processor and whether resellers must use their own merchant credentials.

Talk to a Specialist

Built for Production Recharge, Not a Demo Checkout

Credential isolation

Reseller keys stay on the reseller record. A downline user cannot see or reuse another merchant account.

Idempotent credits

The same gateway payment ID cannot credit twice if a webhook is retried.

Reconcile with reports

Match gateway settlements to panel credit logs when finance closes the month in Mumbai, Dubai, or Nairobi.

See Pricing for license options, or Rent SMPP Application if you want hosted recharge included in a rental stack.

FAQ

Payment Gateway Integration: common questions

Yes. Popular options such as Razorpay, PayU, CCAvenue, Paytm, Cashfree, Stripe, PayPal, Authorize.net, Paystack, and Flutterwave are common starting points, but the integration is built so we can wire the gateway your market already uses. The credit engine stays the same: confirmed payment, then auto credit as configured.

Credits are added only after the payment gateway confirms a successful transaction through its callback or webhook. Failed, pending, or cancelled payments do not change the wallet. The pack size, bonus, tax, and currency rules come from what you configured in the system.

Yes. Each reseller can add their own gateway keys in their panel and start collecting from downline users. Money settles to the reseller merchant account. The platform then auto credits that user wallet according to the reseller pricing packs, not a shared platform merchant account.

The software is used with India-focused gateways (Razorpay, PayU, CCAvenue, Paytm, Cashfree, PhonePe) and with international processors (Stripe, PayPal, Adyen, Mollie, Authorize.net) plus Africa-focused options such as Paystack and Flutterwave. Exact methods (UPI, cards, net banking, wallets) depend on the gateway you wire.

Payment gateway wiring is part of the messaging platform so Admin, Reseller, and User wallets can recharge online. The specific gateway, settlement currency, and pack catalogue are configured per deployment. See Pricing for how add-ons are quoted.

Gateway keys are stored for the Admin or the individual reseller who owns them, not mixed across tenants. Webhook signatures are verified before any credit is posted, and every recharge is written to credit-usage logs for audit.

Client Feedback

What Our Clients Say

Our clients run regulated, high-volume messaging infrastructure and prefer not to be named publicly. These testimonials are shared with permission while keeping commercially sensitive details confidential.

Excellent documentation, responsive technical support, and an enterprise-grade platform that scales as our business grows.
Engineering Manager, SaaS Provider Canada 5 million notifications per month Runs Messaging Platform Client since 2022
We evaluated several messaging platforms before selecting SMPP Center. The deployment flexibility and API capabilities matched our enterprise requirements.
VP of Engineering, Technology Company United States 20+ integrated applications Runs Enterprise SMS Gateway Client since 2020
We needed complete control over our messaging infrastructure instead of relying on a hosted provider. The platform has delivered excellent performance and reliability.
Solutions Architect, Software Company South Korea 99.99% service availability Runs Enterprise Messaging Platform Client since 2020
The delivery reports and routing controls give us the visibility we were looking for. The system has integrated well with our internal applications.
Head of Technology, Enterprise Communications Company South Africa 4 operator routes Runs SMPP Server Client since 2021

Names and company details are withheld at our clients' request. This is common among telecom providers, SMS aggregators, fintech companies, and enterprises that consider their messaging infrastructure commercially sensitive.

LET US WIRE YOUR PAYMENT GATEWAY

Tell us which gateway you use and whether resellers need their own merchant credentials. We will map checkout to auto wallet credit.

TALK TO A SPECIALIST