Paylater Integration & Testing

which is used in and supported by akulaku, kredivo, and indodana as partners integration steps and api used perform order registration direct registration api paylater docid\ rzhpwi4kzady2idps 7j redirect paylater api checkout docid\ fp pvad326g01famucvp5 perform charge direct payment api paylater docid\ mt5y81qfxypavzcwo0hsu redirect payment api checkout docid\ o 4mmsbwxtzib0ydniohw receive callback and push perform check status api direct status inquiry api paylater docid\ c7by1comgvlnauoqjixnx redirect status inquiry api checkout docid\ rhh7pmisd6ihn99ywvjhm optional perform cancel api to cancel direct cancel api paylater docid 7ejz8tcd 0jl1zabi8lmv redirect cancel api checkout docid\ cmiiew1oy21qp7qdecul credential for paylater testing paylater name description indodana phone number 62838499610 otp 999999 pin 123654 paylater testing guide name test steps rules and conditions akulaku uses and access with real account confirm your inquiry your pin otp transaction successful perform with a small amount after receiving success , needs to perform check status first, then next step is to hit confirm receipt api to settle funds to 's side kredivo uses and access with kredivo account confirm your otp transaction successful kredivo is mandatory for every to perform on dev environment and through review with kredivo first perform with a small amount after performing on dev environment, continue to prod environment after is successful, please cancel immediately indodana uses and access with indodana account confirm your detail perform your pin transaction successful indodana is mandatory for every to perform on dev environment and through review with indodana first perform with a small amount failed transaction possible reason not supported by issuer network transaction rejected from integration checklist & test case implement inquiry after receiving callback implement inquiry after receiving inside dbprocessurl review log review firewall setting (eg cloudflare for dbprocessurl setting) check merchanttoken implementation execute test scenarios in development environment execute test scenarios in production environment get sample scenario https //docs google com/spreadsheets/d/e/2pacx 1vqiaimcm0vz3l1ca jkw3yxyipjsb966fg1wtet8qpfdowevuliewooy6i4ujpl3a/pub?output=xlsx review error handling (timeout, failed, negative case) cart data parameter description count total number of all cart data item parameter consist of cart data details item > goods id goods id item > goods detail goods description item > goods name goods name item > goods amt goods price item > goods type goods type item > goods url url to the goods page item > goods quantity goods total item > goods sellers id seller id item > goods sellers name seller name best practice cartdata must not empty used specific dev mid for assure count parameter similar to total goods type assure goods sellers id and goods sellers name filled out similar to sellers on registration when is received on your dbprocessurl , strongly recommend to verify by using inquiry see also paylater payment flow docid\ tnunnbfganfbrqy csepx to find out during with paylater feature docid\ vdnwbq9bgzeltp2xuzqtn to find out features on paylater glossary docid 77uvplxptdbz7majjnulc to find out particular term used on paylater faq docid\ kdb6p0lp4 jvbiean0r2x if you want to find out frequently asked questions related to