Pending recharge
Retain the original action in the customer view. Explain the next checking step without promising a completion time that has not been agreed.
Plan pending outcomesMobile top-up API
Plan a mobile recharge or airtime journey for a wallet, telecom reseller or marketplace. APISMA evaluates private API access using your business model, intended markets and expected volume.
Before confirmation
The sender may be recharging their own phone or someone else’s. Both need a chance to catch a wrong destination before they proceed.
| Planning decision | Customer-facing information | Question for private review |
|---|---|---|
| Recipient number | Country context and a clearly formatted number, shown again before confirmation. | What input format is required? What validation is available, and what does a valid format not prove? |
| Operator | The selected or confirmed operator, with a correction path when necessary. | Is operator identification available for this scope? How are ported or ambiguous numbers handled? |
| Recharge product | Whether the recipient receives airtime value or a specific bundle. | Which products and conditions apply? Do not treat a data allowance as cash-equivalent airtime. |
| Sender and recipient amounts | The relevant charge and received value, with currency labels where applicable. | Which fees, taxes or currency conditions must your interface disclose before confirmation? |
Two different selection experiences
A generic amount picker can be misleading when a recharge product has its own allowance or validity. The interface must reflect the actual agreed product information.
Start with the value and the prepaid service.
Do not leave the sender guessing whether the visible amount is what they pay or what the recipient receives.
Confirm any minimums, denominations or deductions privately. Do not assume that every operator accepts arbitrary amounts.
Start with what is included and for how long.
Name the applicable voice, data or other product entitlement using confirmed product information.
Explain when the bundle starts and any relevant eligibility conditions. A bundle label alone is not enough for an informed choice.
When the result is unclear
Recharge support needs a safe reference, timing and product context. A publicly posted phone number or an automatic second attempt is not a recovery plan.
Retain the original action in the customer view. Explain the next checking step without promising a completion time that has not been agreed.
Plan pending outcomesDistinguish the confirmed processing result from what the recipient sees. Define who can investigate the operator context and what evidence is safe to collect.
Describe intended sender and recipient markets during qualification. A country calling code does not establish operator coverage, commercial eligibility or available recharge products.
Common questions
Do not assume that it does. Prefix-based assumptions can be affected by number portability and local numbering rules. Confirm the identification and validation behavior available for the intended integration.
No. Top-up concerns an existing prepaid service. An eSIM journey concerns a connectivity plan, compatible device and installation or activation steps.
No live operator or coverage list is published here. State the markets and operator questions you need to evaluate, then confirm the account-specific scope privately.
Explain whether you serve wallet customers, telecom resellers or an international recharge audience. Include your work contact, selected category and realistic monthly volume range.
Select mobile top-ups in the form, with your company, work contact and expected volume. Prepare sender, recipient and market questions for the follow-up; do not submit real customer phone numbers.
Submitting a request does not create an account or guarantee approval.