giropay can only process EURO payments.

1. buyer/ customer chooses giropay/ giropay-ID
2. merchant initialises giropay/giropay-ID request (initialise giropay payment)
3. GiroCheckout initialises request at giropay
4. giropay submits response to GiroCheckout
5. merchant gets response about initialisation (if an issue occurs the transaction is finished)
6. merchant sends redirect URL to buyer/ customer
7. the buyer's/ customer's browser redirects to giropay where the bank is selected (optional, only if bank is not already stored in browser)
8. giropay redirects to the customer's online banking
9. bank shows login page
10. buyer/ customer authorises giropay payment/ giropay-ID
11. bank processes reqest
12. bank submits result to giropay
13. giropay submits result to GiroCheckout
14. GiroCheckout notifies merchant about the result (payment result notification)
15. merchant processes result
16. merchant sends HTTP Statuscode to GiroCheckout
17. GiroCheckout sends merchants redirect page to giropay
18. buyer/customer clicks “Zurück zum Shop” and gets redirected to the merchant (buyer redirection)

As shown in the workflow there are different API calls during a giropay transaction.

1. initialise transaction
2. payment result notification to merchant
3. buyer redirection to the merchant (triggered by buyer after the payment or automatically after a few seconds)

The initialization of a giropay can be processed in different ways. This will be distinguished just by the project id.

Towards a successful initialization you receive a reference number and an redirect link. The redirect link leads to the online banking account of the buyer's bank. He has to be redirected to his bank. This can be achieved by a HTTP-Redirect-Header, HTML page with an corresponding Meta-Tag or JavaScript redirect.

URL: https://payment.girosolution.de/girocheckout/api/v2/transaction/start
provided by: GiroCheckout
called by: Merchant

The reply includes a JSON encoded string. The field rc contains the response code. If it is 0 the transaction was successfully initialised. The response also includes a transaction id and a redirect URL to the online banking account of the buyer's bank.

JSON array with item objects:

[ {
    "name" : "Bobbycar",
    "ean" : "800001303",
    "quantity" : 3,
    "grossAmount" : 2599
  }, {
    "name" : "Helm",
    "quantity" : 1,
    "grossAmount" : 1853
  } ]

The result of a initialised transaction will be submitted to the prior in the urlNotify parameter specified URL. This notification should be used to update the payment status in the merchant's system.

The result of a giropay payment is contained in the field gcResultPayment.

At the end of the payment process on giriopay-side, an automatic redirect back to the shop is done after 5 seconds.

URL: notifyUrl of the prior init transaction call
provided by: merchant
called by: GiroCheckout

As a reply to the GET request, one of the following HTTP status codes is expected.

After completing the payment, the customer may return to the merchant through a link. After 5 seconds, there is an automatic redirect.

URL: redirectUrl of the prior init transaction call
Provided by: merchant
Called by: GiroCheckout

This service allows the retrieval of the information associated to the sender of a completed transaction. As a response to the given reference number, the account holder, IBAN and BIC of the customer are returned. This information may be used for a refund to the original payer.

URL: https://payment.girosolution.de/girocheckout/api/v2/giropay/senderinfo
Provided by: GiroCheckout
Called by: Merchant

The response is a JSON object. The rc field returns an error code. If rc = 0 is returned, the corresponding fields contain the sender information.