CVS Integration & Testing

integration steps and api used perform call transaction registration api {{integration}} direct docid 7ldzdpulxqp7ycgigja29 redirect docid\ jmwqygezluwquphbbb3js receive callbacks and push notifications from {{nicepay}} perform api status inquiry {{integration}} direct docid 79r7v9ynenetfidqqvmkk redirect docid 7thqvphz6emwezw5 d4an optional do api cancel {{integration}} to cancel a {{transaction}} direct docid\ wdahsfktq6jxp6jwf791z redirect docid\ nosop1r8knfg81vmkxsc cvs testing guide test steps rules and condition using mid {{merchant}} or mid sandbox ( ionpaytest ) autopaid make a {{cvs}} (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}} {{cvs}} 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 failed transaction possible reason entered incorrectly payno payno expired or not valid rejected from {{partner}} integration checklist & test case 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 https //docs google com/spreadsheets/d/e/2pacx 1vqiaimcm0vz3l1ca jkw3yxyipjsb966fg1wtet8qpfdowevuliewooy6i4ujpl3a/pub?output=xlsx review error handling (timeout, failed, negative case) best practice 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 see also {{visit}} {{the}} docid\ tzvugwxiezp71nxxd8zjl {{page}} to find out {{the}} {{system}} {{process}} during {{payment}} with {{the}} {{cvs}} {{visit}} {{the}} docid\ wgqhy0hdirskzp2jzhoer {{page}} to find out {{the}} {{transaction}} features on {{the}} {{cvs}} {{visit}} {{the}} docid\ nywlus9ndll9diq0zp1an {{page}} to find out {{the}} particular term used on {{cvs}} {{visit}} {{the}} docid\ racnbv 13dhknt2umhhsy {{page}} if you want to find out frequently asked questions related to {{cvs}}