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
  • Testing

Was this helpful?

  1. Integration Guide
  2. Payment Methods & Wallets

giropay

PreviousepsNextGoogle Pay

Last updated 4 months ago

Was this helpful?

giropay transactions can also be processed via the Saferpay JSON API. However, as giropay is a third party provider, there are a few things to consider.

General requirements

  • A and thus a valid identification with a username and password for the Saferpay system.

  • At least one active Saferpay terminal via which payment can be carried out and the associated Saferpay TerminalId.

  • A valid giropay merchant account

  • A valid Merchant Authorization Reference

For giropay activation on the Saferpay terminal, please about your giropay credentials and the desired currency.

Technical requirements

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

  • JSON API Version 1.5 or later

  • giropay restricts the Payment.OrderId to a maximal length of 20 characters. The OrderId will be automatically trimmed if it exceeds the maximal length. Please keep this in mind to properly handle the use of the OrderId.

  • giropay does not support the . .

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

Handling of delivery address

The processing of giropay transactions requires that the delivery address data is submitted. The minimum required delivery address values are:

  • FirstName

  • LastName

  • Zip

  • City

  • CountryCode

If the minimum required delivery data is missing or not complete, the Payment Page delivery address form, will be displayed during the payment process for the cardholder/purchaser to enter or complete the missing values. In this case the delivery address form is displayed regardless of the DeliveryAddressForm configuration (true or false).

Supported features

Feature

Support

❌

Multipart Captures

❌

Secure Card Data

❌

✅

Recurring Payments

❌

3D Secure

❌

Dynamic Currency Conversion

❌

Mail Phone Order

❌

✅

Omni-Channel

❌

giropay transactions (payments and refunds) are captured automatically and will always report:

Transaction.Status: "CAPTURED".

Testing

If the minimum required delivery address values are submitted during the , the delivery address form will not be displayed or will be skipped, except if the DeliveryAddressForm value is set to true.

/

Please refer to, if you want to test giropay .

this chapter
Refunds
Testing
corresponding license
Payment Page
Iframe integration
Capture
Saferpay will break out of the IFrame, if necessary
inform our customer service
Payment Page process
Payment Page initialization
Cancel