logo
English
English
API ReferenceSign In

Best Practices

Last updated 02/17/2021

Optional API parameters and potential usage 

1.`customer id`

Customer ID is an identifier which is returned in the response of Xendit’s customer API (https://developers.xendit.co/api-reference/#customers). The customer object supports storage of customer profiles for businesses and individuals, along with their KYC documentation and other account information. When used in the eWallets API, merchants can keep track of customer payments behaviors and used for analysis as it is returned in the data schema of our payment callbacks.

2. `basket`

The basket array of object supports storage of items purchased by end user and other information about the items. When used in the eWallets API, merchants can link up payments and items data for analysis. These information will be returned in the data schema of our payment callbacks.

  1. `metadata`

The metadata object helps merchants stores additional information which may be useful in their business use case. Merchants can define the key and values of this object. One example of metadata being used is in tagging of transactions based on geographical location or store branches at transaction level. This reduces the need to additional code logic to process data subsequently.

You can specify up to 50 keys, with key names up to 40 characters long and values up to 500 characters long.

Dynamic callback urls

It is strongly recommended that callback URL for payment notifications is set inside Xendit dashboard - callback settings. Doing so would help in security and tracking of where callbacks are sent and received from.

In cases where there is a business or testing need to override the callback URL in dashboard settings, the `callback-url` header parameter can be used. If provided, the value will override the callback URL set in Xendit dashboard.

Was this page helpful?
Yes No