International edition · Frontend test content
This page supports Budyoo international UI, language-switching and reading-flow tests. It is incomplete and is not an effective agreement. Use synthetic test accounts and data; do not enter real sensitive information or make real payments based on this text.
1. Test notice
This page is for recharge-interface and reading-flow tests. It offers no actual product, initiates no charge and does not establish that a balance or virtual item has been credited.
Cover currency formatting, long product names, connection failures and repeated taps without presenting sample prices as actual offers.
2. Products and pricing
Actual products need a name, currency, price, quantity, bonus portion and usage scope. This sample sets no exchange rate, recharge package or delivery deadline.
Display purchased and bonus quantities separately. Format amounts consistently and do not replace the server's order amount with a client calculation.
3. Order and payment states
Creating an order, opening a payment provider, processing, success, failure and cancellation are distinct states. Repeated submissions should follow the actual API's idempotency rules.
A client payment callback should trigger server verification. Read credited funds and balance changes from the server, and show unavailable payment providers accurately.
4. Balances and records
Test screens should distinguish available balances, frozen states and transaction records. A failed request must not be presented as a confirmed zero balance.
Consumption order, bonus handling and expiration depend on actual product configuration. This sample creates no additional spending rules.
5. Exceptions and refunds
This test text does not promise unconditional or immediate refunds or a universal refund percentage. Duplicate charges, missing credits and service issues require review of records and the applicable channel process.
Complete the actual refund policy, exceptions, contact process and timelines when products and channels are known. The sample does not exclude cases that must be handled under applicable rules.
6. Integration checks
Use synthetic order identifiers to test wrapping, copying, dates and status refresh. Do not place payment credentials or real order details in public screenshots or unprotected logs.
Before actual recharge is enabled, verify payment, server checks, accounting, exception handling and associated notices. This page serves frontend development only.
Test scenario
| Test scenario | Expected display |
|---|---|
| Language switching | Show separate text in the selected language |
| Web and mobile | Wrap paragraphs and keep headings and lists readable |
| Long-page reading | Scroll to the end and return to the previous page |
- 1. Test notice
- 2. Products and pricing
- 3. Order and payment states
International edition · Frontend test content
Before release, confirm the operator, valid contacts, service regions, age policy, actual products, data inventory and required review. Saving this test content does not confirm those details.