Welcome to Xendit’s latest documentation. For legacy content, access the previous documentation here or the previous API reference here.

FAQs and technical help

Prev Next
This content is currently unavailable in Indonesian. You are viewing the default (English) version.

Frequently-asked Questions for Sales.

Questions

Answers

How do customers create an account and get access to the products?

We only provide API’s so there is no Iluma Dashboard for clients to sign up and login to. Iluma accounts need to be created internally:

  1. Request for a new account using the workflow in Slack: #data-product-dev

    1. We will generate a Token for the client and unlock access to each product that they need

  2. The client can use the token to generate their API Keys (Test and Live)

  3. Follow this integration guide on making requests and setting up callbacks

  4. We can enable the Test mode API key if the customer has not signed the agreement, so that they get to test the APIs first

  5. Once the agreeement is signed, we can enable the Live API key

The customer is getting PENDING results from their API requests. How can they get the results?

Some of our API’s like Bank Validator are asynchronous. It can take ~1 second on average to get results by:

  1. Setting up a callback / webhook

  2. Using a “Get by ID” API (request ID returned from initial request)

What banks do we support for Bank Validation?

Customers can query all our available Bank Codes using this API. We cover most major banks in Indonesia and Vietnam.

Can we trust the accuracy of these API’s?

  • Our Bank NV relies on the information of our bank networks. It has been proven to be mostly accurate for local-currency bank accounts. Occasionally there can be false-negatives which is often an inaccuracy from one of our connectors.

  • Our KTP Validators rely on the accuracy of our vendors, which are connected directly to Dukcapil. Any inaccuracies can be traced to Dukcapil’s database.