API Changelog - 2026-08-05: Sub-merchant email removed
The subMerchant.email field has been removed from card-based payment
request bodies and response schemas for all card payment methods (card,
visa, mastercard, maestro). In responses, subMerchant.websiteUrl
is now a required field. Payment facilitators must update their
integrations accordingly.
POST /v1/payments — Create Payment
The subMerchant.email field has been removed from the request body for
all card-based payment methods. This is a breaking change: sending
this field will now result in a validation error. Remove it from your
integration.
| Property | Details |
|---|
| Name | paymentMethod.<type>.subMerchant.email |
| Location | Request body |
| Type | string |
| Required | Was required — now removed |
| Format | Email address, max 254 characters |
| Example | "merchant@example.com" |
POST /v1/requests/payments — Create Payment Request
The subMerchant.email field has been removed from the request body for
all card-based payment methods. This is a breaking change: sending
this field will now result in a validation error. Remove it from your
integration.
| Property | Details |
|---|
| Name | paymentMethod.<type>.subMerchant.email |
| Location | Request body |
| Type | string |
| Required | Was required — now removed |
| Format | Email address, max 254 characters |
| Example | "merchant@example.com" |
POST /v1/credits — Create Credit
The subMerchant.email field has been removed from the request body for
all card-based credit methods. This is a breaking change: sending
this field will now result in a validation error. Remove it from your
integration.
| Property | Details |
|---|
| Name | paymentMethod.<type>.subMerchant.email |
| Location | Request body |
| Type | string |
| Required | Was required — now removed |
| Format | Email address, max 254 characters |
| Example | "merchant@example.com" |
POST /v1/requests/credits — Create Credit Request
The subMerchant.email field has been removed from the request body for
all card-based credit methods. This is a breaking change: sending
this field will now result in a validation error. Remove it from your
integration.
| Property | Details |
|---|
| Name | paymentMethod.<type>.subMerchant.email |
| Location | Request body |
| Type | string |
| Required | Was required — now removed |
| Format | Email address, max 254 characters |
| Example | "merchant@example.com" |
GET /v1/payments/{paymentId} — Get Payment
The subMerchant object in payment responses has changed: email has
been removed and websiteUrl is now a required field. Update any
response parsing that relied on email and ensure your integration
handles the presence of websiteUrl.
| Property | Details |
|---|
| Name | paymentMethod.<type>.subMerchant.email |
| Location | Response body |
| Type | string |
| Required | Was not required — now removed |
| Format | Email address, max 254 characters |
| Example | "merchant@example.com" |
| Property | Details |
|---|
| Name | paymentMethod.<type>.subMerchant.websiteUrl |
| Location | Response body |
| Type | string |
| Required | Now required |
| Format | URL, max 256 characters |
| Example | "https://example.com" |
GET /v1/transactions/{transactionId} — Get Transaction
The subMerchant object in transaction responses has changed: email
has been removed and websiteUrl is now a required field. Update any
response parsing that relied on email and ensure your integration
handles the presence of websiteUrl.
| Property | Details |
|---|
| Name | paymentMethod.<type>.subMerchant.email |
| Location | Response body |
| Type | string |
| Required | Was not required — now removed |
| Format | Email address, max 254 characters |
| Example | "merchant@example.com" |
| Property | Details |
|---|
| Name | paymentMethod.<type>.subMerchant.websiteUrl |
| Location | Response body |
| Type | string |
| Required | Now required |
| Format | URL, max 256 characters |
| Example | "https://example.com" |