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

Overview

Prev Next

Payment Session is an all-in-one solution provided by Xendit, offering a Xendit-hosted page for handling payments. It is a low-code integration designed to simplify implementation and support a wide range of payment flows. With Payment Session, you can offload the complexities of managing checkout pages while ensuring a good payment experience for your customers.

Mode options

Mode

Description

PAYMENT_LINK

The default and standard mode that redirects the end user to a Xendit-hosted page to complete the payment.

CARDS_SESSION_JS

Used for card payments when you host your own checkout page but require Xendit's library for compliance. (See CARDS_SESSION_JS documentation for more details)

Available request types

Request type

Description

SAVE

Use this type to save only the end user's payment information. You will receive a payment_token_id that can be used for future transactions. This is useful if your registration event is separate from your payment event, or if you need the user to store their payment method before initiating a payment (e.g., for recurring payments registration).

PAY

Use this type to collect a single payment. You will receive a payment session object contains payment_request_id as the payment confirmation. Additionally, you can also obtain a payment_token_id if you set up PAY and store the payment method details in one go.

*This is currently only available for CARDS_SESSION_JS mode option.

Integration flow

You can see the integration flow for some use cases here.