Back to use cases

Communication credits and virtual numbers

Email, SMS, VoIP, eSIM, and Virtual Number Services

Sell email, SMS, VoIP, eSIM, and virtual-number credits with payment status before numbers, minutes, or traffic are provisioned.

Practical guide

Collect communication service credits without making customers wait for manual balance updates.

Communication services often bill by credits, numbers, seats, traffic, or prepaid plans. Customers need balance added quickly because messages, calls, or eSIM activations may depend on it.

Crypto can fit global customers and teams buying services from countries where card or bank payments are awkward.

MakePay can create payment links or API payments for top-ups, renewals, number rentals, and usage balances with status that can update the account.

Payment examples

SMS credit top-up
eSIM package checkout
Virtual number renewal
VoIP minutes invoice

Why it works

Payment status can trigger credit or number provisioning
Wallet checkout works for global customers without local cards
Links can be sent from dashboards or support chat
Settlement lands in the merchant-controlled wallet path

Problems solved

Credits and numbers must be tied to the right account
Card rules can be strict for telecom-like services
Manual top-up proof causes support delays
Short renewals need fast confirmation

Guide

Why communication credits need fast reconciliation

A customer topping up SMS or VoIP balance often expects service to continue immediately. Manual matching creates avoidable support pressure.

The payment request should carry account ID, product type, and amount so the balance update is traceable.

Usage can stop suddenly

Paid status should drive account credit or renewal.

Accounts need metadata

Payments must map to the right workspace, number, or plan.

International buyers fit

Stablecoins can make cross-border top-ups easier.

Guide

How MakePay fits communication billing

Start with manual top-up links, then connect API and webhooks to credit balances or renew numbers automatically.

The checkout page stays branded while settlement routes toward the provider wallet.

Top-up links

Good for customers who ask support for crypto payment.

Automated credits

Webhook status can add balance after payment.

Direct settlement

Merchant funds do not need to sit in platform custody.

Setup path

Start with one clear payment moment.

Step 1

Choose the credit type

Define SMS, call, eSIM, number, or email plan amount.

Step 2

Create the account payment

Attach customer or workspace metadata.

Step 3

Update balance after payment

Use dashboard status first or webhooks when automated.

Step 4

Log the top-up

Keep payment and balance history together.

Questions

Plain answers before you launch.

Can this update credits automatically?

Yes, when webhook status is connected to the provider's account system.

Is this only for prepaid services?

No. It can also collect renewals, setup fees, or overdue balances.

More use cases

Explore nearby merchant types