Payment Methods Index (Supportbot Routing)
This index helps support agents and bots quickly identify how each service is paid:
- account balance
- crypto payment flow
- both
- no direct checkout
Use this file as the first routing step before answering payment-related questions.
What problem does this solve?
Users need clear guidance on Payment Methods Index — including how it works, what it costs, and how to complete the flow inside SORN.
How SORN helps
This index helps support agents and bots quickly identify how each service is paid:
- account balance
- crypto payment flow
- both
- no direct checkout
Use this file as the first routing step before answering payment-related questions.
Main features
- Fast payment-method lookup per service
- Clear separation of checkout types
- Supportbot-friendly wording for intent routing
- Links naturally to service-specific documentation
Common questions
User mixes services
Ask for exact module name before giving payment advice.
User assumes one payment method works everywhere
Explain that payment support is service-specific.
User reports missing balance option
Verify whether that service/product supports balance at all.
Tip: Always answer payment questions with service-specific wording
Always answer payment questions with service-specific wording.
Tip: For uncertain cases, confirm the exact service and subpage first
For uncertain cases, confirm the exact service and subpage first.
Tip: Never promise a payment method that is not listed for that service
Never promise a payment method that is not listed for that service.
Related SORN products
When to use this
User asks: "Can I pay AnoGift with balance?" -> Route to **Crypto-only** -> answer: No, AnoGift uses crypto checkout. User asks: "Why does AnoCard only show crypto for this card?" -> Route to **Both (product-dependent)** -> explain that some card products are crypto-only. User asks: "Where do I need to top up first?" -> Route to **Balance-only** services. User asks: "How do I add funds to balance?" -> Route to **Top Up** service documentation.
Important notes
- Always answer payment questions with service-specific wording.
- For uncertain cases, confirm the exact service and subpage first.
- Never promise a payment method that is not listed for that service.
- Use `topup.md` for all account-funding questions.
- **User mixes services:** Ask for exact module name before giving payment advice.
- **User assumes one payment method works everywhere:** Explain that payment support is service-specific.
- **User reports missing balance option:** Verify whether that service/product supports balance at all.
Availability, fees, and partner requirements may vary depending on provider, route, region, amount, and selected service.