API Changelog - 2026-06-02: Summary
The subMerchant.phoneNumber field is no longer required for card-based
payment methods (Card, Visa, Mastercard, Maestro). Integrations acting as
payment facilitators may now omit the phone number when submitting
sub-merchant data.
POST /v1/payments — Create Payment (Card-based methods)
The phoneNumber field inside the subMerchant object has been made
optional for all card-based payment methods (card, visa, mastercard,
maestro). Previously, omitting phoneNumber in the sub-merchant data
would result in a validation error. Integrations that do not have a
sub-merchant phone number available no longer need to supply a placeholder
value.
| Property | Details |
|---|---|
| Name | paymentMethod.<type>.subMerchant.phoneNumber |
| Location | Request body |
| Type | string |
| Required | No (optional) — previously required |
| Format | Phone number, max 16 characters |
| Example | "+31201234567" |
GET /v1/payments/{paymentId} — Get Payment
The phoneNumber field inside the subMerchant object in payment
responses is no longer guaranteed to be present. Integrations reading
sub-merchant data from payment responses should treat phoneNumber as
an optional field.
| Property | Details |
|---|---|
| Name | paymentMethod.<type>.subMerchant.phoneNumber |
| Location | Response body |
| Type | string |
| Required | No (optional) — previously required |
| Format | Phone number, max 16 characters |
| Example | "+31201234567" |