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
  • Checking the status
  • Testing

Was this helpful?

  1. Integration Guide
  2. Payment Methods & Wallets

Click to Pay

PreviousblikNextDiners Club International & Discover Card

Last updated 2 months ago

Was this helpful?

Click to Pay transactions can be processed via the Saferpay Payment Page, without much effort from your side. Note that Click to Pay is not a classic means of payment, but rather a digital wallet. Your customers will still pay with Visa, Mastercard, or whatever credit card has been saved inside the wallet, thus the actual recorded payment method will correspond to this. However, Saferpay will also return information that this transaction has been performed through Click to Pay. Furthermore, all options and limitations of the used means of payment apply, if not mentioned otherwise in this chapter.

The following chapter will guide you through the steps required in order to activate and use Click to Pay.

General requirements

The handling of Click to Pay 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 by which payments can be carried out and availability of the associated Saferpay TerminalId.

    • Availability of at least one active contract on said terminal, for the given payment method you want to process.

Technical requirements

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

  • Click to Pay must be pre-selected using the Wallets parameter ().

Direct selection

Unlike other payment Methods, Click to Pay must be pre-selected via the Wallets parameter, with "CLICKTOPAY" being the only value. You also must not use Wallets and PaymentMethods together. Otherwise, Click to Pay will not be displayed.

This also means, that Click to Pay cannot be displayed alongside other payment methods and wallets.

{
    "RequestHeader": {
        "SpecVersion": "[CURRENT SPECVERSION]",
        "CustomerId": "[YOUR CUSTOMERID]",
        "RequestId": "[YOUR REQUESTID]",
        "RetryIndicator": 0,
        "ClientInfo": {
            "ShopInfo": "My Shop",
            "OsInfo": "Windows Server 2016"
        }
    },
    "TerminalId": "[YOUR TERMINAL]",
    "Payment": {
        "Amount": {
            "Value": "12345",
            "CurrencyCode": "EUR"
        },
        "OrderId": 123,
        "Description": "Test Order #123"
    },
    "Wallets": [
        "CLICKTOPAY"
    ],
    "ReturnUrl": {
        "Url": "[YOUR URL]"
    },
}

Supported features

Since Click to Pay is not a classical payment method, but a digital wallet, the supported features depend on the payment means, that are used.

Furthermore, the merchant can only accept payment methods, that are activated on the specified terminal Id.

The payment means within the wallet are then processed via the normal processors.

For example: If a card holder selects his Visa card, the card is then processed as such, through Click to Pay as the wallet.

Activation

Click to Pay is a self-service protocol, meaning, that you have full control over its activation.

Select the terminal from the drop-down, where you want Click to Pay to be activated on and scroll down to Self Service.

Simply check the switch to activate Click to Pay, or the Click to Pay Simulator for the test-environment.

Checking the status

By clicking on the State button on the right side in the activation-section, you can check the status of your Click 2 Pay activation for the available payment methods.

Testing

Saferpay does offer an extensive Click to Pay simulator. All test-cases are controlled through the simulator-ui. Please refer to the Activation section, to activate the Click to Pay simulator.

Furthermore, please consider the following specifics:

The simulator option actually presents you with two separate testing environments, as also mentioned in the simulator-ui:

The card entry form is directly connected to the Click to Pay sandbox and requires their test cards, as well as a Click to Pay sandbox account to work.

However even these cards may not be able to fully process.

The usage of the simulator cases (see below) is preferred instead.

However the bottom section under Click to Pay Simulator Controls are part of the Saferpay simulator and present you with premade test-cases, for easier testing. This is the preferred method for testing, as they do not require any access to the Click to Pay sandbox.

As of now, is NOT supported for Click to Pay.

To activate Click to Pay, please log into the and navigate to .

The will not work with this form. You must use the test cards, that will be provided to you by Click to Pay.

Secure Card Data
Saferpay Test-cards
corresponding license
Payment Page
see below
Saferpay Backoffice
Settings => Payment Means / Terminals