PostFinance Pay
Via the Saferpay JSON API, payments can be handled through PostFinance Pay.
General requirements
Acceptance of PostFinance Pay requires:
A corresponding license and thus a valid identification with a username and password for the Saferpay system.
A valid contract with PostFinance.
Technical requirements
The general integration of PostFinance Pay can be done via the Payment Page and has the following requirements for integration:
JSON API Version 1.37 or later.
Recurring payments are only available via Alias.
Postfinance Pay does not support the Iframe integration. Saferpay will break out of the IFrame, if necessary.
The
Payment.OrderId
is restricted to a maximum of 18 characters. Anything more will be truncated.
PostFinance Pay transactions are only valid for 30 days and must be captured in this time frame. After 30 days, the reservation will void and the authorized amount can no longer be transferred! However you have a guaranteed payout, within these 30 days.
Refunds may only be executed up to 12 months, after the original transaction.
Supported features
Feature
Support
3D Secure
❌
Dynamic Currency Conversion (DCC)
❌
Mail Phone Order
❌
Omni-Channel
❌
Storage in the Secure Card Data Store
If you intend on saving PostFinance Pay-data for later use, Saferpay provides the possibility of storing the payment data inside the Saferpay Secure Card store, for the Payment Page and the Standalone Alias Registration. For this, the following requirements must be met:
Activation of Saferpay Secure Card Data in the Saferpay merchant account.
The feature must also be activated on PostFinance side.
Stansdalone registration
If you intend to use the standalone registration, you need to specify the parameter Type with the value POSTFINANCEPAY, which signals, that you want to save Postfinance Pay payment means.
Address collection from PostFinance
This function is currently not yet available and will be delivered at a later date.
Testing
Please refer to this chapter, if you want to test PostFinance Pay.
Last updated