CVS Integration & Testing

11 min

Integration Steps and API Used

Test Steps	Rules and Condition
Using MID Merchant or MID sandbox ( IONPAYTEST) AutoPaid. Make a Convenience Store (CVS) registration. Write down or print payment code. Bring the payment code to Indomaret or Alfamart / Alfamidi / Dan+Dan / Lawson. Check your payment inquiry. Pay according to the nominal listed. Take your payment receipt. Transaction success. Check your (dbProcessUrl) notification.	Notify the cashier that a payment has been made using NICEPAY+Merchant's name. CVS can be cancelled and returned after payment, but can only be done manually or after the validity period of the payNo number has expired. Cannot be installed via API. Convenience Store number (payNo) can expire by default in the 7th day but also depending on the Merchant's preferences, settings can be adjusted (the most common are 24 hours, 3 days, etc). Terms based on CVS: Alfamart & Alfamidi: transactions cannot be made after 10 p.m. and can be used again after 1 a.m. on the next day. Indomaret: transactions cannot be made after 11 p.m. and can be used again after 1 a.m. on the next day.

Implement Inquiry status after receiving the callback.

Implement Inquiry status after receiving the notification inside dbProcessUrl.

Review payment logs.

Review firewall settings (eg. cloudflare for the dbprocessUrl).

Check the merchantToken implementation.

Execute scenario tests in Development Environment.

Execute test scenarios in Production Environment. Get Sample Scenario

Review Error Handling (Timeout, Failed, Negative Case).

payValidDt and payValidTm are used to set the payment deadline for Merchants who use these parameters.

When your dbProcessUrl notification is received, NICEPAY strongly recommends Merchant to verify notifications using the Inquiry API.

Notification Handling is useful to minimalize Fraud action. NICEPAY strongly recommends Merchant to verify Notification Handling.