- Introduction
- TLS Security and Communication Settings
- Licenses and Interfaces
- PSD2
- Payment Page Interface
- Saferpay Fields
- Transaction Interface
- Secure Card Data
- Recurring Payments
- Refunds via API
- Inquire Interface
- Mobile App integration
- IFrame Integration and CSS
- Partial Captures
- Marketplace
- Secure PayGate REST API
- Fraud Prevention
- API Health Check
- Mastercard Issuer Installments
- FAQ
- Payment means for testing
-
Demo
- Saferpay Demo Environment
-
Payment Method specifics
- Credit Cards
- Masterpass
- TWINT
- PayPal
- BillPay
- Swiss Postcard
- SOFORT by Klarna
- Klarna Payments
- eps
- paydirekt
- iDeal
- SEPA
- ePrzelewy
- Alipay
- Bancontact
- ApplePay
-
Additional Information
- Saferpay Blog
- Contact
- API Specification
- Changelog
ePrzelewy
ePrzelewy payments can be processed with Saferpay without much effort. This chapter describes what needs to be considered in this regard.
Requirements
The handling of ePrzelewy payments with Saferpay requires:
- The corresponding Saferpay eCommerce licence and thus the existence of a valid identification with a username and password for the Saferpay system.
- Availability of at least one active Saferpay terminal via which payment can be carried out and availability of the associated Saferpay TerminalId.
- A valid ePrzelewy contract.
- The Payer.DeliveryAddress.Email-parameter is mandatory and needs to be set, with the initial request, or captured through the respective form.
- ePrzelewy is only available via the PaymentPage flow!
- NotifyUrl: The NotifyUrl is mandatory, in order to avoid missing payment successes. See the Payment Page process for further information!
Attention: For ePrzelewy activation on the Saferpay terminal, please inform our activation service cs.ecom@six-payment-services.com about your pRzelewy merchant account ID and the desired currency.