# Change Log

## v0.5.21 (2026-06-11)
- **Updated Create Payment Intent Guide**
  - Removed static guidance for Thailand installment payments (`INSTALLMENT`): Deleted redundant static information as dynamic specifications (banks, terms) are now provided via the Get Payment Capacity (EBP_API_240) API.

## v0.5.20 (2026-06-04)
- **Billing Account API - Create Payment Method (v0.2)**
  - Added the following fields to the `NAVER_PAY` payment method metadata (`metadata`):
    - `purchaserName`: Purchaser's name (required for payments in insurance and high-risk categories)
    - `purchaserBirthday`: Purchaser's date of birth (required for payments in insurance and high-risk categories)

## v0.5.19 (2026-06-07)
- **Enhancement of Payment Capacity API Data Specification**
  - Added response fields for Payment Capacity (EBP_API_240): Included `capabilities` object for each payment method, providing flags for direct payment support (`supportsDirectPay`) and saving support (`supportsSave`).
  - Normalized Omise installment specification field names: `min` to `minAmount`, `max` to `maxAmount`, and `installmentTerm` to `availableTerms`.

## v0.5.18 (2026-05-29)
- **Added SDK Short-lived Token API**
  - Added new SDK Short-lived Token (EBP_API_221) API specification and integration guide: Defined the specifications and fallback validation mechanism for a 5-minute short-lived secure token required for client-side SDK integration without signature validation.

## v0.5.17 (2026-05-22)
- **Added New API Data Specification**
  - Added new Get Payment Capacity (EBP_API_240) API: Defined the interface specification for pre-transaction lookup of available payment methods and PG-specific metadata (e.g. Thailand installment banks and monthly terms) based on store and country codes.
- **Added SDK Integration Guide**
  - Added EBP SDK Guide: Added instructions on pre-checking supported PG information via the Payment Specification Inquiry API and enforced the mandatory use of the timestamp (`t`) parameter for cache busting.

## v0.5.16 (2026-05-19)
- **Supplemented API Data Specifications**
  - Updated the Create Payment Method (EBP_API_120) API: Changed the requirement for the `email` field from mandatory (`Yes`) to optional (`Optional`).
...
## v0.5.15 (2026-05-14)
- **Updated Getting Started Guide**
  - Added Server Connection and Firewall Configuration Guide: Reflected connection path (OMS(AWS)-Corporate Network-EBP(AWS)) and firewall setup instructions.
  - Added Environment-specific IP Range Information: Specified IP ranges for DEV/QA and PRD (KIC, AIC, EIC).

## v0.5.14 (2026-04-27)
- **Improved API Data Specifications**
  - Updated the response structure for the Payment Creation (EBP_API_230) API: Enhanced the structure from `response.data.pgResponse.data` to `response.data.pgResult.pgResponse` to ensure terminology intuition and consistency.

## v0.5.13 (2026-04-25)
- **Supplemented API Data Specifications**
  - Updated the Get Payment Methods (EBP_API_109) APIs to include the `createdAt` field in the response.
  - Updated the Create Payment Intent (EBP_API_224) APIs to include the `createdAt` field for payment methods (savedPaymentMethods) in the response.

## v0.5.12 (2026-04-22)
- **Updated Webhook Guide**
  - Updated the Payment Authorized (`PAYMENT_AUTHORIZED`) Webhook documentation: Added technical notes regarding the possibility of skipping authorization webhooks during auto-capture and the non-guaranteed sequence of events.

## v0.5.11 (2026-04-21)
- **Supplemented API Data Specifications**
  - Updated the Create Payment Intent (EBP_API_224) API: Added the `autoCapture` field to determine whether to automatically capture the payment.
  - Updated the response structure for the Payment Creation (EBP_API_230) API: Moved the `status` field into `instructions` and supplemented the integration guide.
  - Updated the response data schema for the Get Payment Methods (EBP_API_109) API to include: `userNo`, `billingAccountNo`, `paymentMethod`, `pgProvider`, and `pgChannel`.
  - Renamed Data Specification Value: Changed `SAVED_METHOD` to `SAVED_PAYMENT_METHOD` in the `paymentInstrumentType` field to ensure terminology consistency.

## v0.5.10 (2026-04-17)
- Improved response structure for Create Payment Intent (EBP_API_224), Payment Creation (EBP_API_230), Create Payment Method (EBP_API_120), and Complete Payment Method Registration (EBP_API_121) APIs
  - Separated business result data (`data`) and process control instructions (`instructions`) to enhance readability and integration convenience.
  - Moved control fields such as `nextStep`, `requiresClientAction`, `clientAction`, `requiresFollowUpApi`, and `followUpApi` into the `instructions` object.
  - The `status` field has been moved into the `instructions` object to clarify its role in client state control.
  - The `paymentUrl` field is maintained within the `data` object as business result data.
- Updated guide for Payment Creation API (EBP_API_230)
  - Removed unnecessary common header links from the request headers section.
  - Corrected the referenced field name in the `X-EBP-Context` header description (`paymentContext` → `paymentHeaderContext`).

## v0.5.9 (2026-04-16)
- Updated guide for Create Payment Method API (EBP_API_120)
  - Added `orderNo` (Order number) field to the response data schema.
- Updated Webhook guide for Payment Voided (`PAYMENT_VOIDED`)
  - Refined documentation following the separation of refund events and changed to void-specific fields (`voidedAmount`, `voidedAt`).
- Newly added Webhook guide for Payment Refunded (`PAYMENT_REFUND_RECEIVED`)
- Newly added Webhook guide for Payment Refund Requested (`PAYMENT_REFUND_REQUESTED`)
- Improved Common Webhook Data Schema
  - Renamed all webhook response fields from `paymentStatusCode` to `paymentStatus` for consistency.

## v0.5.0 (2026-04-01)
- Initial release