PayPal
Paypal payments can be processed with Saferpay without much effort. This chapter describes what needs to be considered in this regard.
The handling of PayPal 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 PayPal merchant account.
Feature | Support |
✅ | |
✅ | |
Batch Close | ❌ |
Secure Card Data | ❌ |
✅ | |
Recurring Payments | ❌ |
3D Secure | ❌ |
Dynamic Currency Conversion (DCC) | ❌ |
Mail Phone Order | ❌ |
✅ | |
Omni-Channel | ❌ |
✅ | |
✅ |
PayPal refunds do not need to be captured and will always report a
Transaction.Status: "CAPTURED".To enable processing of PayPal payments via Saferpay a few settings must be first specified in the PayPal Mercahnt account.
(click to enlarge)
(click to enlarge)
(click to enlarge)
(click to enlarge)
Enter
be-sfp_api1.six-group.com into the Third Party Permission box and click on Lookup.
(click to enlarge)
Tick the following checkboxes and then click on Add:
- Use Express Checkout to process payments.
- Issue a refund for a specific transaction.
- Authorize and capture your PayPal transactions.
- Obtain information about a single transaction.
- Search your transactions for items that match specific criteria and display the results
- Obtain authorization for pre-approved payments and initiate pre-approved transactions.
- Accept or deny a pending transaction.
- Issue a refund for any prior transaction.
For PayPal activation on the Saferpay terminal, please inform our activation service about your PayPal merchant account ID and the desired currency.
Saferpay will return the following error-message, if PayPal ha snot been set up correctly:
{
"ResponseHeader": {
"SpecVersion": "[CURRENT SPECVERSION]",
"RequestId": "[YOUR REQUESTID]"
},
"Behavior": "ABORT",
"ErrorName": "TRANSACTION_DECLINED",
"ErrorMessage": "Transaction declined by acquirer",
"TransactionId": "[TransactionId]",
"ErrorDetail":[
"Check that PayPal was setup as described in the Saferpay integration guide for the PayPal payment method."
],
"ProcessorName": "PayPal",
"ProcessorResult": "invalid_request",
"ProcessorMessage": "No permission to set target_client_id",
"OrderId": "[YOUR ORDERID]"
}
The general integration of PayPal can only be done via the Payment Page and requires the following things to be noted:
- The notification URLs, inside the
Notificationconatiner are mandatory, in order to avoid missing payment successes. See the Payment Page process for further information. - PayPal requires the
Payment.OrderIdto be unique. Saferpay however does not limit the use of the OrderId in any way. If you use PayPal, you have to make sure, that your system submits unique OrderIds for every PayPal-transaction, otherwise you will get an error-message during the authorization. - PayPal does not support the Iframe integration. Saferpay will break out of the IFrame, if necessary.
- Unlike normal transactions, PayPal refunds always have the status CAPTURED, thus executing the money right away.
PayPal does not support the iFrame Integration!
PayPal actively blocks the iFrame-Integration. In order to circumvent this issue, the Saferpay Payment Page will break out of the iFrame and display the PayPal website full-size, in order to make a payment possible. However, please keep in mind, that the ReturnUrls will also be displayed full-size!
Unlike credit cards, that give the merchant a certain guarantee for the authorized money, PayPal reserves the right to deny the payout of a transaction, if the solvency of the account holder changes negatively after the authorization.
The PayPal Seller Protection protects eligible transactions from chargebacks, reversals and their associated fees!
Precondition to profit from the Seller Protection is to send the delivery address of your customer over our API. The delivery address (http://saferpay.github.io/jsonapi/#Payment_v1_PaymentPage_Initialize - Container DeliveryAddress) needs to be the same as the Billing Address.
The SellerProtectionStatus can have three results in your request:
Eligible
Partially Eligible
Not Eligible
Please check this link how to integrate the Seller Protection: http://saferpay.github.io/jsonapi/#Payment_v1_PaymentPage_Assert
After clicking the link, please scroll a little bit down until the Point "PaymentMeans", click on "Object" and on PayPal.
Saferpay offers a way to implement a so called "Express Checkout", which allows the merchant to gather every important information about the payer -like addresses etc.- from the payment gateway, without the need of capturing this data yourself.
The payer could go through a guest-checkout, pays his order and everything needed for the merchant is returned at the end.
This minimizes user-interaction, makes the checkout sleek and fast, which increases the user-satisfaction.
Last modified 1mo ago