Paylater Integration & Testing
Paylater which is used in the integration and testing process supported by Akulaku, Kredivo, and Indodana as Partners.
Integration Steps and API Used
- Perform Order Registration API integration.
- Direct: Registration - API Paylater.
- Redirect: Paylater - API Checkout.
- Perform payment Charge API integration.
- Direct: Payment - API Paylater.
- Redirect: Payment - API Checkout.
- Receive NICEPAY callback and push notification.
- Perform Check Status API integration.
- Direct: Status Inquiry - API Paylater.
- Redirect: Status Inquiry - API Checkout.
- Optional: perform Cancel API integration to cancel the transaction.
- Direct: Cancel - API Paylater.
- Redirect: Cancel - API Checkout.
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 |
| 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 |
|
|
Indodana |
|
|
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
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
Visit the Paylater Payment Flow page to find out the system process during payment with the Paylater.
Visit the Paylater Feature page to find out the transaction features on the Paylater.
Visit the Paylater Glossary page to find out the particular term used on Paylater.
Visit the Paylater FAQ page if you want to find out frequently asked questions related to Paylater.