NumFlow FAQ
Answers about virtual numbers, SMS verification orders, wallet holds, cancellation, and API usage.
When a number is assigned, NumFlow places a hold for the displayed platform price. The hold is captured only after the first SMS verification code is received. If no code arrives and the order is canceled or times out successfully, the held amount returns to available balance.
Yes. Select the service first, then review currently available countries, lines, and platform prices before creating an order.
Check the order status and expiry window before creating another order. If the order is still pending and no SMS arrives, use the cancel flow when it is available.
Yes. Send a unique Idempotency-Key for each business request so repeated attempts do not create duplicate order effects.
After logging in, use the account and wallet pages to review balance, recharge-code records, transactions, and API keys.
Use the expiry shown by the order page or the expires_at value returned by the API. Within that effective window, keep querying the same order for later codes instead of creating a duplicate order.
Authenticated immediate responses include the number and verification code needed for the active task. History and audit views use masked references where full content is not required.
Yes. Use account-scoped API keys, idempotent ordering, rate-limit handling, and order-expiry checks to build controlled server-side workflows.
Review the help center for order-specific guidance or open your account to inspect active orders.