A little clarity goes a long way
Let’s keep things simple.
Answers for customers testing DataVibely and owners preparing a safe data-selling launch.
How the purchase journey works
Find your fit
Choose a network, compare sizes and validity, and enter the recipient’s number.
Payment comes first
Explore device checkout or Paystack sandbox, with no real money charged.
Track the outcome
View your reference and test a successful or failed delivery experience.
Frequently asked questions
Does test mode charge money or send data?
No. Interface tests save only a test record on this device. Optional Paystack sandbox checkout uses test credentials and also does not charge real money. Test delivery outcomes never contact a supplier.
Can I launch without prefunding a supplier wallet?
No compatible no-prefunding API arrangement has been verified for this app. VTpass offers a hosted reseller website, but its standalone API documentation describes debiting a supplier wallet. For DataVibely to fulfill orders using your own Paystack payments without upfront capital, a supplier must confirm a postpaid or per-transaction settlement contract and provide a compatible API. No such contract is connected here.
Why can’t a confirmed Paystack payment fund delivery immediately?
Confirmation means a transaction has succeeded, not that funds have arrived in your bank account. Paystack lists next-working-day automated NGN payouts in Nigeria. A supplier must offer credit, postpaid settlement, or a documented per-transaction payment arrangement to bridge that gap.
Where are the small bundles?
In test mode, all four networks include sample 100MB, 200MB, 300MB, and 500MB bundles. Plans are sorted by size by default, with daily, weekly, monthly and bonus filters. A live catalogue must show every plan actually returned by the provider; an unavailable size cannot be invented.
Are the bundle prices live network prices?
No. The main bundle list clearly uses sample prices for testing. Integrations includes a separate read-only supplier catalogue fetch. Those provider listings are not purchasable until the settlement arrangement and live delivery API are verified.
How are repeat payments and deliveries prevented?
The device test flow reuses an existing unpaid order for the same number and plan, and only permits valid status transitions. A completed test order cannot be paid again. Live protection requires server-side unique payment references, atomic fulfillment locking, signed webhooks, and provider idempotency; live payments are blocked until those are implemented.
Will my history follow me to another device?
Not yet. Interface test orders are explicitly saved on this device. A live launch needs authenticated server-side order storage; local storage must not be used for live financial records.
What happens if real delivery fails?
A production supplier integration must support transaction status queries, safe idempotent retries, and a reconciliation/refund policy. The current test flow lets you explore failed delivery and retry states without making any real payment or supplier request.
Ready for your first test connection?
No funding needed to test. No real charge. Just a feel for the flow.