--- title: Paylater Integration & Testing slug: en/paylater-integration-and-testing description: Information about integration and testing on the Paylater payment method with the NICEPAY system image: https://archbee-image-uploads.s3.amazonaws.com/ZHvSjR5ZrsoxwKbJa3xmo/uQtHnIlZcA0RYYFmDpXaB_nicepay-docs-logo.png icon: {"faIcon":"fa-solid fa-book"} docTags: createdAt: 2022-09-16T09:04:45.000Z --- Paylater which is used in the integration and testing process supported by Akulaku, Kredivo, and Indodana as Partners. # Integration Steps and API Used *** 1. Perform Order Registration API integration. - Direct: [Registration - API Paylater](docId\:rzhpWi4kzady2Idps_7J-). - Redirect: [Paylater - API Checkout](docId\:Fp_pvad326g01FaMUCVp5). 2. Perform payment Charge API integration. - Direct: [Payment - API Paylater](docId\:mt5y81QFXYPaVZCWo0hSU). - Redirect: [Payment - API Checkout](docId\:o-4MmsbwXtZIb0ydniohw). 3. Receive NICEPAY callback and push notification. 4. Perform Check Status API integration. - Direct: [Status Inquiry - API Paylater](docId\:C7bY1comgVlnAUoQJixnx). - Redirect: [Status Inquiry - API Checkout](docId\:RhH7PmISd6IHN99yWVJHm). 5. Optional: perform Cancel API integration to cancel the transaction. - 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 | 1. Uses and access with the real account. 2. Confirm your payment inquiry. 3. Input your PIN. 4. Input OTP. 5. Transaction successful. | Perform testing with a small amount.
After receiving the success notification, the Merchant needs to perform the Check Status API first, then the next step is to hit the Confirm Receipt API to settle the funds to the Merchant's side. | | Kredivo | 1) Uses and access with Kredivo account. 2) Confirm your payment. 3) Input OTP. 4) Transaction successful. | - Kredivo integration is mandatory for every Merchant to perform testing on the dev environment and through the review process with Kredivo first.  - Perform testing with a small amount.  - After performing testing on the dev environment, continue to the prod environment. After the transaction is successful, please cancel immediately. | | Indodana | 1. Uses and access with Indodana account. 2. Confirm your transaction detail. 3. Perform payment. 4. Input your PIN. 5. Transaction successful. | - Indodana integration is mandatory for every Merchant to perform testing on the dev environment and through the review process with Indodana first.  - Perform testing with a small amount. | # Failed Transaction Possible Reason *** - Not supported by Issuer network. - Transaction rejected from the Partner. # Integration Checklist & Test Case *** - [ ] Implement inquiry status after receiving the callback. - [ ] Implement inquiry status after receiving the notification inside `dbProcessUrl`. - [ ] Review payment 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 Merchant testing. - Assure the `count` parameter similar to the total goods type. Assure `goods_sellers_id` and `goods_sellers_name` filled out similar to the `sellers` on Registration. - When notification is received on your `dbProcessUrl`, NICEPAY strongly recommend Merchant to verify the notification by using the Inquiry API. # See also ::::VerticalSplit{layout="middle"} :::VerticalSplitItem Visit the [Paylater Payment Flow](docId\:tNunnBfganfbrQY-Csepx) page to find out the system process during payment with the Paylater. ::: :::VerticalSplitItem Visit the [Paylater Feature](docId\:VDnWbq9bgZelTP2XuzqTn) page to find out the transaction features on the Paylater. ::: :::: ::::VerticalSplit{layout="middle"} :::VerticalSplitItem Visit the [Paylater Glossary](docId:77uVplXPtDBZ7majjNUlc) page to find out the particular term used on Paylater. ::: :::VerticalSplitItem Visit the [Paylater FAQ](docId\:kDB6P0LP4-JvBiEaN0R2x) page if you want to find out frequently asked questions related to Paylater. ::: ::::