Glossary
Term | Definition |
---|---|
Account Linking | For the case of credit cards, e-wallets, or direct debit, there is an option for you to let your end customer link their account to your system, so that it would be easier for your customer to make the subsequent payment. |
Close/dynamic amount | Virtual Account, QR, or OTC can only accept payments with a predetermined nominal. Close-Amount will require you to set the Expected-Amount field or the amount that Xendit can accept. |
Customer Object | The Customer Object is a standard data structure to hold information relating to one of your customers. It has the following major components. This object will be used for Ewallet, Direct Debit, and Cards Integration |
Link & Pay | Creates a reusable payment method then creating a payment transaction in a single flow. |
Multiple use | Payment Method can receive payment more than once and only will become inactive when it has passed its expiration date. |
One-time use / Single Use | Payment method can only receive payment successfully once and will become expired afterward |
Open/static amount | Any money-in product can accept payments for any nominal value from your end customer. |
Pay then Link | Your end customer will have one flow when making a payment then their account automatically will be linked to your system for the subsequent payment. |
Payment Method | Represents the instrument, source, or mode of payment. This can be a tokenized reusable payment source or a one-off payment. |
Payment Object | The Payment Object unifies callback notifications across all money-in channels |
Payment Request | Represents the intent to pay and initiate a transaction. |
Settlement | The Process of money movement from issuing bank to acquiring bank. |
Tokenized payment / Subsequent payment | Your end customer will make a payment based on the linked account |
Withdrawal | All businesses can send funds from their Xendit Balance to their chosen destination bank account. |
Last Updated on 2023-06-02