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
  • Prerequisites
  • Creating a Payment Page Configuration
  • Configuration Options
  • Styling
  • E-mail notification
  • Terms
  • Preview
  • Configuration Overview

Was this helpful?

  1. Interfaces
  2. Backoffice
  3. Settings

Payment Page Configuration

Payment Page Configurations provide a simple yet powerful way to customize the payment experience of your customers

PreviousUser AdministrationNextOnline Support

Last updated 4 days ago

Was this helpful?

This guide is a supplement to the Saferpay Backoffice user manual. It describes the configuration options available for the creation of templates for the Saferpay Payment Page in the Saferpay Backoffice.

A Payment Page Configuration can be used to amend the look and technical parameters for the Saferpay Payment Page without any additional programming work. The JSON API PaymentPage/Initialize parameters listed here in monospace are described in the documentation.

Prerequisites

The prerequisites for using and configuring the Saferpay Payment Page are as follows:

  • A corresponding Saferpay eCommerce license and therefore a valid ID with a user name and password for the Saferpay system.

  • At least one active Saferpay terminal via which payments can be made and the associated Saferpay CustomerId and TerminalId.

  • A valid acceptance contract for credit cards or other means of payment.

Creating a Payment Page Configuration

After logging into the Saferpay Backoffice, select the "Settings" area to arrive at the "Payment Page configuration":

A short introduction will be displayed:

Click on the "Create new configuration" button to create a new template. The following screen is displayed:

Configuration Options

Styling

This section enables you to upload your own logo to be displayed on the payment page and to set the colors and fonts for the payment page.

Supported file-types are GIF, JPG, JPEG, PNG, SVG and WEBP with a maximum file size of 1MB. The pictures will be automatically scaled. We recommend to use a WEBP file if possible.

E-mail notification

You can enable payment notification emails and remove personal data such as name, address, IBAN, etc.

Terms

The label for payment process term and for the pay button can be adapted to your requirements.

Preview

Changes to the payment page configuration are immediately displayed in the preview window.

Configuration Overview

As soon as a configuration has been created, it will be added to the overview:

  1. Click to view details of the configuration.

  2. Displays the ConfigSet value to be entered to use a configuration.

  3. If a configuration has been set as the "Default", it will always be used without the need to state the ConfigSet parameter.

  4. Displays the status of a configuration.

  5. Deletes an existing configuration.

  6. Produces a copy of an existing configuration.

The customization options are divided into different areas. Changes to the payment page configuration are immediately displayed in the .

preview window
Saferpay Payment API