Skip to main content
Before enabling production mode, a complete test cycle is vital to ensure that demand states at Back Office have been correctly updated.

​
1. Test data for Sandbox

The test data are held at a central page so that you can re-use them without duplicating information within this guide:

Open Test Data

Check cards, Yapeand other sandbox scenarios from a single reference.

Validate in Test Mode

Be sure that the module remains at Sandbox before you run your validation purchases.
In PrestaShop, this guide focuses on order conduct, states and certification, and concrete data live with shared reference.
To test asynchronous methods as PagoEfectivo or QR in Sandboxcontact our support team if you need to simulate payment confirmation.

​
2. Certification cycle

To secure a note 10/10 Check these 4 key points for implementation:
1

Purchase Flow

Reconduct a complete order and check that you are redirected to the “Confirmed demand!” in PrestaShop.
2

Automatic Status Change

Confirms that order will pass from “To be paid” a “Payment accepted” after a successful transaction ( S2S).
3

Reversal Test

Executs an cancellation from the order and valid that the status changes to Repaid.
4

Log Review

Check that table payme_logs properly register data entry and output without timeout errors.

​
3. Support considerations

Our team of integrators are available to review your results and support you with production.
  • Availability: The environment Sandbox is active 24/7.
  • Support Hours: Monday to Friday, 09: 00 AM to 06: 00 PM (working days).
  • Time Zone: All logs and supports are run by hour Peru (GMT -5).

​
4. Contact channels

Once your tests have been completed, send the results to those responsible for integration:

Integration

posstorea.authentication @ alignet.com

Customer care

(01) 700-8377

Problem solving

Something doesn’t work as you thought? Check our common bug guide at PrestaShop.