Changelog UP API - Payments - Ecommerce API
This page contains a log of all changes made to the Payments - Ecommerce API documentation. It is organized by date, with the most recent changes listed first.
2026-07-03: Scheme response codes in failed operation responses
The failed transaction status now returns dedicated response schemas
with paymentMethod.scheme.responseCode for all operations and their
webhook notifications. Succeeded card scheme details are also expanded
with the scheme response code. Visa authorizations gain a new
responseCodeCategory field.
View detailed changelog for 2026-07-03
2026-06-25: Metadata field added across all payment operations
A new metadata field is now available in all payment operation
request bodies (payments, cancels, captures, increments, refunds, and
credits), as well as in all corresponding response and webhook
payloads. The field accepts up to 50 key-value string pairs for
cross-referencing and reconciliation. The merchantAdviceCode field
in Mastercard payment method responses is now formally deprecated.
View detailed changelog for 2026-06-25
2026-06-25: Token status added to payment responses
The paymentMethod.token.status field is now included in payment and
transaction responses for tokenized Visa, Mastercard, Maestro, and Troy
card payments, indicating whether the token is active or suspended.
View detailed changelog for 2026-06-25
2026-06-24: FPX bank code unification
FPX bank codes now use a _business suffix to distinguish B2B codes from
retail codes. Six legacy B2B codes have been replaced, and the
commercialTransactionType field is deprecated.
View detailed changelog for 2026-06-24
2026-06-16: Scheme response codes in transaction responses
Scheme response codes are now returned in declined transaction responses. Declined webhook payloads have also been updated to include the raw scheme response code.
View detailed changelog for 2026-06-16
2026-06-02: Sub-merchant phone number made optional
The subMerchant.phoneNumber field is no longer required for card-based
payment methods (Card, Visa, Mastercard, Maestro). Payment facilitators
may now omit the phone number when submitting sub-merchant data in payment
requests.
View detailed changelog for 2026-06-02
2026-05-19: Klarna Network distribution support added
Klarna has been re-introduced as a supported payment method with Klarna
Network distribution support. A new POST /v1/paymentMethods endpoint
is defined for retrieving available payment methods with Klarna-specific
display data. New fields klarnaNetworkData and
klarnaNetworkSessionToken are available in the Klarna passthrough
object.
View detailed changelog for 2026-05-19
2026-05-06: Klarna payment method decommissioned
The klarna enum value has been removed from the paymentMethod.type field
and all Klarna-specific schemas have been removed from the API. Integrations
using Klarna must migrate to a supported payment method.
View detailed changelog for 2026-05-06
2026-04-27: Remove Masterpass wallet type
The masterpass enum value has been removed from the wallet type field for
Card, Maestro, Mastercard, and Visa payment methods. Masterpass is no longer
supported. Integrations using masterpass must switch to a supported wallet
type.