API change Log

This page provides the LINE Pay API change log, starting with the most recent updates.

November 2025

In Taiwan, operators licensed by the competent authority to engage in businesses such as collecting and making payments for actual transactions as an agent, accepting stored value funds, and handling domestic or international small-amount remittances are referred to as electronic payment institutions (EPI). These institutions are all subject to the legal and institutional regulations of the Act Governing Electronic Payment Institutions. Accordingly, in addition to the existing Online API v3 and Offline API v2, the following APIs are added:

• Online API v4
• Offline API v4
• Offline API v2.4

If you want to apply only EPI-related changes from Offline API v2, use Offline API v2.4. To use Offline API v4 instead of Offline API v2, you must also change the authentication method. For more details, see Prerequisites.

LINE Pay updates the API to indicate, as follows, which type of company will handle payments and settlements so that merchants can be informed when a transaction is completed:

• "TSP": Third-party Service Provider, provider of existing payment methods.
• "EPI": Electronic Payment Institutions

If you don’t need to know the type of payment provider during transactions, you can continue to use the legacy API.

As of now (May 2025), the new version of the API can be tested in a sandbox environment.

To test EPI type transactions, use the My code generator at the URL below. However, EPI type transactions are not valid in the online payment scenario, so the paymentProvider field in the API response will always indicate "TSP" for Online API.

• EPI Credit Card
  • https://sandbox-web-pay.line.me/web/sandbox/payment/oneTimeKey?countryCode=TW&paymentMethod=card&preset=18
• EPI Balance
  • https://sandbox-web-pay.line.me/web/sandbox/payment/oneTimeKey?countryCode=TW&paymentMethod=balance&preset=3

Here is a summary of each API change.

• Online API v4 Changes
• Offline API v4 Changes
• Offline API v2.4 Changes

Online API v4 changes

• To provide EPI information, info.paymentProvider field added to the following API responses:
  • Confirm payment (POST /v4/payments/{transactionId}/confirm)
  • Capture (POST /v4/payments/authorizations/{transactionId}/capture)
  • Retrieve payment details (GET /v4/payments)
  • Request pre-approved payment (POST /v4/payments/preapprovedPay/{regKey}/payment)
• Added options.regPayRequest field, related to pre-approved payment settings, in request parameter for the Request payment (POST /v4/payments/request) API

Offline API v4 changes

• Applied new authentication method (HMAC) in HTTP request headers (same as online API v3, v4).
• Removed server allowlist (IP allowlist) settings.
• Changed request parameters for the Request payment (POST /v4/payments/oneTimeKeys/pay) API.
• To provide EPI information, info.paymentProvider field added to the following API responses:
  • Request payment (POST /v4/payments/oneTimeKeys/pay)
  • Check payment status (GET /v4/payments/orders/{orderId}/check)
  • Retrieve confirmation information (GET /v4/payments/authorizations)
  • Capture (POST /v4/payments/orders/{orderId}/capture)
  • Retrieve payment details (GET /v4/payments)

Offline API v2.4 changes

• To provide EPI information, info.paymentProvider field added to the following API responses:
  • Request payment (POST /v2.4/payments/oneTimeKeys/pay)
  • Check payment status (GET /v2.4/payments/orders/{orderId}/check)
  • Retrieve confirmation information (GET /v2.4/payments/authorizations)
  • Capture (POST /v2.4/payments/orders/{orderId}/capture)
  • Retrieve payment details (GET /v2.4/payments)

May 2025

Due to the termination of LINE Pay Japan service, the following content has been removed:

• Deposit API, which was exclusive to Japan, is no longer available.
• Explanations related to some Japan-specific fields in the Online and Offline APIs are no longer provided.