Owing to the merge of the giropay and paydirekt companies, the giropay API is currently subject to several changes. This page gives you all the necessary information that will help you assess whether you need to adapt your integration on your end or not, and if so, which changes are needed.

• You will find the documentation for the current/new API here: New API documentation
• The old documentation for the previous giropay API is still available for reference here: Legacy API documentation
• An overview of the differences between the old and new APIs can be found here: Differences and similarities of both APIs

In this section, we will detail what exactly you need to consider when preparing your system for the new giropay.

Please select your most relevant subject from the following list:

• Changes to the GiroCheckout API
• Integration via an SDK
• Municiapl Customers - Direct integration
• Municiapl Customers - Payment Page
• Merchant Customers - Direct integration
• Merchant Customers - Payment Page
• Comparison old and new API
• Frequently asked questions

1. The fields bic, iban and the info fields (info1Label, info1Text etc.) are no longer available.
   The required information regarding the client's bank are now directly obtained on the side of giropay and/or the customer bank and are no longer sent along in the initialization request. Please remove these fields from your request if you are still using them.
2. Information regarding the shopping cart contents can be optionally passed along in the cart field.

1. The shoppingCartType should now be always present in a giropay transaction.
2. The field is optional but impacts other fields of the API.
3. Possible values:
   • PHYSICAL = All goods in the cart are of a physical nature, shippingAddresseFirstName, shippingAddresseLastName, shippingZipCode, shippingCity and shippingCountry are mandatory.
     All other fields may be passed optionally (see API documentation).
   • DIGITAL = All goods in the cart are of a digital nature (require no shipping), shippingAddresseFirstName, shippingAddresseLastName and shippingEmail are mandatory.
     All other fields may be passed optionally (see API documentation).
   • MIXED = The cart contains both physical and digital goods (this is the default value should the parameter not be given), shippingAddresseFirstName, shippingAddresseLastName, shippingZipCode, shippingCity and shippingCountry are mandatory.
     All other fields may be passed optionally (see API documentation).
   • ANONYMOUS_DONATION = This is an anonymous donation and not a commercial transaction (no address data necessary),
     All other fields may be passed optionally (see API documentation).
   • AUTHORITIES_PAYMENT = This is a payment for local authorities (no address data necessary).
     All other fields may be passed optionally (see API documentation).

The SDKs (PHP, Java, .NET) are already up to date and support the new giropay. You can find the documentation under the following links:

• PHP-SDK
• Java-SDK
• .NET-SDK

Transactions with the shoppingCartType “AUTHORITIES_PAYMENT” don't need to pass any further mandatory fields.

Transactions with the shoppingCartType “AUTHORITIES_PAYMENT” for municipal customers don't need to specify any additional mandatory fields.

1. The fields bic, iban and the info fields (info1Label, info1Text etc.) are no longer available.
   The required information regarding the client's bank are now directly obtained on the side of giropay and/or the customer bank and are no longer sent along in the initialization request. Please remove these fields from your request if you are still using them.
2. Information regarding the shopping cart contents can be optionally passed along in the cart field.

1. The shoppingCartType should now be always present in a giropay transaction.
2. The field is optional but impacts other fields of the API.
3. Possible values:
   • PHYSICAL = All goods in the cart are of a physical nature, shippingAddresseFirstName, shippingAddresseLastName, shippingZipCode, shippingCity and shippingCountry are mandatory.
     All other fields may be passed optionally (see API documentation).
   • DIGITAL = All goods in the cart are of a digital nature (require no shipping), shippingAddresseFirstName, shippingAddresseLastName and shippingEmail are mandatory.
     All other fields may be passed optionally (see API documentation).
   • MIXED = The cart contains both physical and digital goods (this is the default value should the parameter not be given), shippingAddresseFirstName, shippingAddresseLastName, shippingZipCode, shippingCity and shippingCountry are mandatory.
     All other fields may be passed optionally (see API documentation).
   • ANONYMOUS_DONATION = This is an anonymous donation and not a commercial transaction (no address data necessary),
     All other fields may be passed optionally (see API documentation).
   • AUTHORITIES_PAYMENT = This is a payment for local authorities (no address data necessary).
     All other fields may be passed optionally (see API documentation).

No special changes are required here.

The current version of our list of frequently asked questions and their answers is available in German and English through the following links.

German FAQ

English FAQ