Available payment channels

  • Updated on Jul 8, 2026
  • Published on Sep 18, 2024
  • 25 minute(s) read
Prev Next

This table provides a high level overview on payment channels available via Xendit and their corresponding features. You can use filter or search to find information about specific payment channels.

More information about columns and values

Column Name

Description

Channel code

Unique identifier for the payment channel, used in API integration.

Display name

Branding name of the payment channel that end users will see during their payment journey.

Currency

Currency supported by the payment channel (e.g., IDR, PHP, USD).

Country

Country where the payment channel can be used.

Type

Category or flow for payment channels (e.g., e-wallet, bank transfer, card, over-the-counter, etc.). This will be useful for grouping payment channel in checkout page.

Min. amount

Floor value that can be collected via this payment channel.

Max. amount

Ceiling value that can be collected via this payment channel.

Settlement time

Business Days — Settlement happens on working days (Monday to Friday, excluding weekends and public holidays).
Timeline: T+X means X working days after payment confirmation.
Example: If a payment is confirmed on Friday with T+2, the settlement will arrive on Tuesday (assuming Monday is not a holiday).

Calendar Days — Settlement happens every day, including weekends and public holidays.
Timeline: T+X means X days after payment confirmation.
Example: If a payment is confirmed on Friday at 3 PM with T+2, the settlement will arrive on Sunday at 3 PM.

Instant — Settlement happens almost right away.
Timeline: usually within 5 minutes of payment confirmation.
Example: If a payment is confirmed on Friday at 3 PM, the settlement will arrive by around 3:05 PM the same day.

Save

Feature for linking or tokenizing payment information for future use is available.

Reusable payment code

Feature for collecting multiple payments via one payment code is available (e.g. a static QR code in physical stores).

Display name

Business name that end users will see during their payment journey.

User approval flow

Redirect — End users will be redirected on their device to log in and authenticate the transaction.

Present to customers — End users will be presented a payment code for them to take action on a separate device / application.

Skip — End users involvement are not required to complete payment.

Push Notification — End users will need to complete the payment on payment channel partner app.

Merchant-initiated transactions

Feature for merchants to collect money without involving end users is available.

Payment processing time

Time delay between end user completing payment step until the payment is confirmed by the payment method provider.

Business days — Payment result occurs approximately after 24 hours * T+X from payment initiated, excludes weekend or public holidays.

Instant — Payment result occurs approximately a few minutes from payment initiated (most of payment channels’s behavior).

Custom payment code

Feature to configure the payment code with specific values is available.

Installments

Feature for end user to break down the payment is available and served by the payment method provider.

Auth & capture

Two-step  payment process: Auth (authorization) to reserve funds, followed by Capture to settle the funds.

Partial capture

Ability to capture less than the authorized amount.

Multiple partial capture

Ability to capture the authorized amount in several parts until fully captured.

Desktop support

Payment channel is supported on desktop devices.

Mobile support

Payment channel is supported on mobile devices.

Display merchant name

Merchant business name displayed to the end user during the payment process.

The displayed name can be:

  • Your business name

  • Xendit's name

  • Your business name prefixed with "Xendit"

Customize display name

Customize the name displayed to the end user during the payment process.

For example, you can customize the name associated with a Virtual Account so that it displays your customer's name instead of the default merchant name.

Payment request expiry (hours)

Duration in hours before a payment request expires if not completed.

Payment token validity (years)

Maximum validity period of a saved payment token.

Refund

Feature for returning full collected amount to user is available via the original payment route.

Partial refund

Feature for returning a subset of collected money to user is available via the original payment route.

Multiple partial refund

Feature for merchants to return funds in multiple partial refunds until the full collected amount is refunded.

Refund validity (days)

Maximum number of days after the original transaction that a refund request can be made.

Payment link

Whether the channel supports creation of a hosted payment page (payment link) for collection.

Fund flow

The settlement funds routing from the end user to the merchant.

Aggregator - will be settle to Xendit’s account balance

Gateway - directly settle to merchant’s bank account