Русский
Українська
Հայերեն
ქართული
Қазақша
Español
Français
Deutsch
Italiano
فارسی
Article focus
Make the commercial website clear to customers and reviewers
Public terms and contacts are part of a trustworthy payment journey.
Before submitting a website for review, publish clear information about the business, offered goods or services, prices, contacts and the conditions of sale or delivery. The cancellation and refund policy should state the applicable rule even when an offer is non-refundable.
Privacy and personal-data processing information must match the actual collection and use of customer data. Keep the same required commercial information available in the Armenian version and in other languages offered by the site.
- Publish contacts and prices.
- Publish terms, privacy and data-processing information.
- State cancellation and refund conditions.
- Keep mandatory information consistent across site languages.
Prepare backend verification and protected endpoints
HTTPS alone does not make a payment flow reliable.
Use HTTPS, but also verify final payment status on the backend rather than trusting a success redirect. Callback or webhook endpoints need provider-appropriate authentication, replay protection where applicable and idempotent processing.
The backend must validate amount, currency and order identifier, then record a traceable status transition. Keep sensitive information out of ordinary logs and restrict administrative access to payment controls.
- Verify payment status server-side.
- Protect callbacks and process retries safely.
- Log normalized events with restricted sensitive data.
Run a readiness review before launch
Test the entire flow from the public page to the order and operational result.
Review the customer journey in each published language and verify that legal and commercial pages are reachable from the payment path. Test both successful and unsuccessful payment paths, including a customer return without a final provider result.
Confirm who owns production monitoring, support escalation, refund handling and content updates. Provider-specific requirements can change, so complete a final check against the current provider terms before go-live.
- Test success, failure and pending paths.
- Check public legal and commercial pages.
- Assign ownership for support and updates.
FAQ
Is HTTPS required for vPOS connection?
HTTPS is a baseline requirement, but reliable payments also need backend verification and protected callback handling.
Can a site accept payment without a cancellation and refund policy?
The applicable cancellation and refund conditions should be published, including an explicit non-refundable rule where relevant.
What should happen after a success redirect?
The backend should verify the provider result before changing the business order status.
