Release 12.11.2025
Changelog
Customer Data in Payout Field Retrieval:
The Retrieve Required Payout Fields endpoint now accepts a new optional customer field in the request body. Allows passing customer information for more accurate payout field determination
Documentation
This features is not yet implemented and is expected in future releases. The structure and implementation details may change.
New Integration Guides:
-
H2H Integration for Instructions): Guide for implementing shop-hosted integration with instruction-based payment methods. This integration enables merchants to receive payment instruction parameters directly via host-to-host (H2H) communication without redirecting to a payment page.
-
Payout via Payment Page: New documentation for creating payouts with minimal required fields and collecting additional recipient information through a payment page.
Orders
Shop Hosted Integration - payer.cardData Field Update:
In the Create Order endpoint, the payer.cardData field is now optional and nullable. This provides more flexibility when implementing shop-hosted integration for instruction-based payment methods that do not require card data
Payment Instruction Parameters - operationReference Field:
The Retrieve Order Details and Callback endpoint now returns a new optional operationReference object array.
Note: This is a preliminary object structure. The field structure and naming may change in future updates.
See the H2H Integration for Instructions) documentation for implementation details.
Payouts
Payout via Payment Page Support:
The Create Payout Request endpoint now returns a new optional payoutLink field in the 201 response:
- Contains the payment page URL when additional recipient information is required
- Only present when recipient details are incomplete
- Enables recipients to securely complete their payout information on a hosted page
- See the Payout via Payment Page documentation for integration details