LogoLogo
BlogLogin
English
English
  • An Introduction to Saferpay
    • Licensing
      • Legacy licensing
    • Reconciliation
    • Acquirers & Payment Methods
    • Web Shop Plugins and certified partners
      • ePages Beyond
      • ePages NOW
      • Magento 2
      • Odoo
      • PrestaShop
        • PrestaShop User Guide
      • Salesforce Commerce Cloud
      • SAP Commerce Cloud
      • Shopware 6
        • Shopware 6 User Guide - German
        • Shopware 6 User Guide - English
      • WordPress WooCommerce
      • Shopify
    • Supported Languages
    • Common Saferpay terms - Glossary
  • News
    • Changes for transactions without customer presence
    • Changes for the Saferpay Hosted Forms, Fields and Payment Page
  • Quick Links
    • Web Shop Plugins and certified partners
    • Secure PayGate
    • User Administration
    • Payment Page Configuration
    • Risk Management
    • API Authentication
  • Interfaces
    • Payment API (aka JSON API)
    • Management API
    • Backoffice
      • The Home screen
      • Batch Processing
      • Transactions
        • Transaction Details
        • Batch Close
        • Declined transactions
        • Pending authorizations
        • Analytics
        • SEPA Refunds Export
        • Authorization & Payment
        • Credit
      • Risk Management
      • Secure PayGate / Payment Links
      • Secure Card Data
        • Secure Card Data Details
      • Settings
        • JSON API basic/Client Certificate authentication
        • User Administration
        • Payment Page Configuration
      • Online Support
      • User Profile
    • Saferpay OnSite
    • Feedback
  • Integration Guide
    • Integrating Saferpay
    • Ways of integration
      • General Information
        • Data Security and PCI DSS
        • Versioning
        • 3-D Secure
        • PSD2
        • Dynamic Currency Conversion
        • Iframe Integration and CSS
        • Fraud Intelligence
          • Silver
          • Fraud Intelligence Integration
      • Payment Page
        • Payment Page checklist
      • Transaction Interface
        • Recurring Payments
        • Refunds
          • SEPA Refunds
      • Capture and Daily Closing
        • Partial Captures
          • Marketplace
      • Secure Card Data - Tokenization
      • Saferpay Fields
      • Inquire Interfaces
      • Mobile Integration
      • Omni-Channel
      • Mail Phone Order
      • Error Handling
      • API Health Check
      • Saferpay API Specification
    • Payment Methods & Wallets
      • General and special cases
      • Account-to-Account Payments
      • Alipay+
      • Apple Pay
      • American Express
      • Bancontact
      • Billie
      • blik
      • Click to Pay
      • Diners Club International & Discover Card
      • eps
      • giropay
      • Google Pay
      • iDEAL 2.0
      • JCB
      • Klarna Payments
      • Maestro International
      • Mastercard
      • paydirekt
      • PayPal
      • PostFinance Pay
      • Przelewy24
      • Reka
      • SEPA Direct Debit
      • Sofort by Klarna
      • TWINT
      • UnionPay
      • Visa & V PAY
      • WeChat Pay
      • WL Crypto Payments
    • Testing
    • Go-Live
    • Frequently Asked Questions
    • Saferpay Demo
      • Saferpay Demo Environment
      • Saferpay Demo Shop
    • Support
    • Changelog
Powered by GitBook
On this page
  • General requirements
  • Technical requirements
  • Supported features
  • Activation
  • To grant permissions to a third party:
  • Activation on your Saferpay Terminal
  • Error response in case of missing permissions
  • Capture and the solvency of the customer
  • PayPal Seller Protection
  • Express Checkout
  • Testing

Was this helpful?

  1. Integration Guide
  2. Payment Methods & Wallets

PayPal

PreviouspaydirektNextPostFinance Pay

Last updated 1 month ago

Was this helpful?

Paypal payments can be processed with Saferpay without much effort. This chapter describes what needs to be considered in this regard.

General requirements

The handling of PayPal payments with Saferpay requires:

  • A and thus 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.

Technical requirements

The general integration of PayPal can only be done via the and requires the following things to be noted:

  • PayPal requires the Payment.OrderId to 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!.

  • Unlike normal transactions, PayPal refunds always have the status CAPTURED, thus executing the money right away.

  • The notification URLs, inside theNotification conatiner are mandatory, in order to avoid missing payment successes. See the for further information.

Supported features

Feature

Support

✅

✅

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".

Activation

To enable processing of PayPal payments via Saferpay a few settings must be first specified in the PayPal Merchant account.

To grant permissions to a third party:

  1. Under Account and Security, click Account Access.

  2. In the Selling online section, click Update next to API access. You can grant or update the NVP/SOAP API permissions to your third party.

  3. On the API Access page, click Grant API Permission.

  4. Enter be-sfp_api1.six-group.com into the Third Party Permission box and click on Lookup.

    When using the test environment in combination with a Paypal sandbox account, the following value must be entered instead: paypal-api-caller_api1.saferpay.com

  5. On the Add New Third Party Permissions page, select the following permissions so that Paypal transactions can be processed via Saferpay: - 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.

Activation on your Saferpay Terminal

Error response in case of missing permissions

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]"
}

Capture and the solvency of the customer

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.

PayPal Seller Protection

Express Checkout

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.

Testing

/

You can add a third-party developer to your account on the page.

Log in to with your Business account.

For PayPal activation on your Saferpay terminal, please about the terminalId(s) you want PayPal to be activated on, your PayPal merchant account ID and the desired currencies.

Therefore Saferpay claims the money directly, once the of the transaction has been successfully executed. If the money cannot be claimed, the capture then returns an error. We generally recommend to execute the as soon as possible, to avoid any issues.

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 ( - 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: After clicking the link, please scroll a little bit down until the Point "PaymentMeans", click on "Object" and on PayPal.

More information about the PayPal Seller Protection you will find on the PayPal Documentation .

Please , in order to know, how you integrate an Express Checkout.

Please refer to , if you want to test PayPal.

Add New Third Party Permissions
PayPal
Capture
Capture
http://saferpay.github.io/jsonapi/#Payment_v1_PaymentPage_Initialize
http://saferpay.github.io/jsonapi/#Payment_v1_PaymentPage_Assert
here
Multipart Captures
Refunds
Testing
PayPal Seller Protection
Express Checkout
corresponding license
Payment Page
iFrame Integration
inform our customer service
Capture
Cancel
(click to enlarge)
Saferpay will break out of the IFrame, if necessary
Payment Page process
refer to this chapter
this chapter