Integration
Credit Card
Direct Debit
Bluecode
eps
giropay
iDEAL
Maestro
PayPal
Payment Page
Tools
Error codes
Result codes
Test data
Sidebar
de
enen:girocheckout:eps:start
Table of Contents
eps
eps can only process EURO payments.
test data
| field | value |
|---|---|
| BIC | HYPTAT22XXX |
| Verfügernummer/-name und PIN | no input needed, click Login |
| mobile TAN | any or empty |
transaction result
| result code | answer | description |
|---|---|---|
| 4000 | successful transaction | After submission of the form by using the data above you create a successful transaction. |
| 4900 | unsuccessful transaction | After clicking the button Zahlung abbrechen you create an unsuccessful transaction. |
workflow
- buyer/ customer chooses eps and enters his bank's BIC
- merchant initialises eps (initialise eps payment)
- GiroCheckout initialises request at eps
- eps submits response to GiroCheckout
- merchant gets response about initialisation (if an issue occurs the transaction is finished)
- merchant sends redirect URL to buyer/ customer
- the buyer's/ customer's browser redirects to eps where the bank is selected (optional, only if bank is not already stored in browser)
- eps redirects to the customer's online banking
- bank shows login page
- buyer/ customer authorises eps payment
- bank processes reqest
- bank submits result to eps
- eps submits result to GiroCheckout
- GiroCheckout notifies merchant about the result (payment result notification)
- merchant processes result
- merchant sends HTTP Statuscode to GiroCheckout
- GiroCheckout sends merchants redirect page to eps
- buyer/customer clicks “Zurück zum Shop” and gets redirected to the merchant (buyer redirection)
API functions
Overview
As shown in the workflow there are different API calls during an eps transaction.
- check bankstatus
- initialise transaction
- payment result notification to merchant
- buyer redirection to the merchant (triggered by buyer)
check bankstatus
This call should not be used anymore. All eps transactions now use an external bank selection form!
This API call checks, if a bank supports the eps payment method. Therefore the BIC of the buyer's account has to be submitted. The response shows if the bank provides eps. It is recommended to do this prior to an initial payment, to make sure that the buyer's bank supports eps.
API call
URL: https://payment.girosolution.de/girocheckout/api/v2/eps/bankstatus
provided by: GiroCheckout
called by: merchant
POST parameter
| parameter | mandatory | type | description |
|---|---|---|---|
| merchantId | yes | Integer | Merchant ID of an eps project |
| projectId | yes | Integer | Project ID of an eps project |
| bic | yes | String(11) | the buyer's bank account BIC (8 or 11-digits), which schould be checked |
| hash | yes | String(32) | HMAC MD5 hash over all API call params (see hash generation) |
example
curl -d "merchantId=1234567" \
-d "projectId=1234" \
-d "merchantTxId=1234567890" \
-d "bic=HYPTAT22" \
-d "hash=818a60dde0fbaeb5e7f5affe7c2a28a7" \
https://payment.girosolution.de/girocheckout/api/v2/eps/bankstatus
reply
The reply contains an encoded JSON string. A response code is submitted in the field rc. If the response contains rc = 0, the bank supports eps. If eps is supported, additional information can be found in the eps parameter. Additional information about the bank will also be returned, if they are known.
JSON parameter
| name | mandatory | type | description |
|---|---|---|---|
| rc | yes | Integer | error codes |
| msg | yes | String(255) | additional informationen about the response code |
| bic | yes | String(11) | BIC |
| bankname | yes | String(100) | name of the bank |
| eps | yes | Integer | 0 = eps payment is not supported 1 = eps payment is supported |
| HEADER parameter | |||
| hash | yes | String(32) | HMAC MD5 hash overall the JSON string. (see api call reply) |
example
hash : 9c26067e25e2d273c6da1fb2be35999a
{"bankcode":"57000","bic":"HYPTAT22XXX","bankname":"HYPO TIROL BANK AG","eps":"1","rc":0,"msg":""}
eps issuer bank request
This call should not be used anymore. All eps transactions now use an external bank selection form!
Returns a list which contains all supported eps issuer banks. The buyer has to choose his one.
URL: https://payment.girosolution.de/girocheckout/api/v2/eps/issuer
provided by: GiroSolution AG
called by: Händler
POST parameter
| name | mandatory | type | description |
|---|---|---|---|
| merchantId | yes | Integer | Merchant ID |
| projectId | yes | Integer | Project ID |
| hash | yes | String(32) | HMAC MD5 hash (see hash generation) |
example
curl -d "merchantId=1234567" \
-d "projectId=1234" \
-d "hash=02f123fdb8b2056596abc0e6ebb1a8c3" \
https://payment.girosolution.de/girocheckout/api/v2/eps/issuer
reply
The reply contains an encoded JSON string. An response code is submitted in the field rc. If the response contains rc = 0, the request was successful.
JSON parameter
| name | mandatory | type | description |
|---|---|---|---|
| rc | yes | Integer | error codes |
| msg | yes | String(255) | additional informationen about the response code |
| issuer | optional | Mixed | list of all supported issuer banks containing bic as key and name |
Beispiel
hash : 68fef295c525df124fe47760fcf12396
{"issuer":{"BAWAATWWXXX":"BAWAG P.S.K. Bank für Arbeit und Wirtschaft und Österreich", "OBKLAT2LXXX":"Oberbank AG","BTVAAT22XXX":"Bank für Tirol und Vorarlberg AG", [...]},"rc":0,"msg":""}
Initialize eps payment
The initialisation of an eps can be processed in different ways. This will be distinguished just by the project id.
Torwards a successful initialisation 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.
request
URL: https://payment.girosolution.de/girocheckout/api/v2/transaction/start
provided by: GiroCheckout
called by: merchant
POST parameter
| name | mandatory | type | description |
|---|---|---|---|
| merchantId | yes | Integer | merchant ID of an eps project |
| projectId | yes | integer | project ID of an eps project |
| merchantTxId | yes | String(255) | unique transaction id of the merchant. Allowed characters: any letters (incl. language-specific special characters such as German Umlauts), 0-9, symbols & = + , : ; . _ ! ? # / |
| amount | yes | Integer | if a decimal currency is used, the amount has to be in the smallest unit of value, eg. Cent, Penny |
| currency | yes | String(3) | currency EUR = Euro |
| purpose | yes | String(27) | purpose |
| bic | deprecated | String(11) | This parameter must not be used anymore. All eps transactions now use an external bank selection form! BIC (8 or 11-digits) |
| urlRedirect | yes | String(2048) | URL, where the buyer has to be sent after payment |
| urlNotify | yes | String(2048) | URL, where the notification has to be sent after payment |
| kassenzeichen | optional | String(255) | Optional field that allows passing an additional reference/identifier for the transaction. This value is displayed inside GiroCockpit as part of the transaction details (and soon export) and a search for it is also supported there. Characters must comply with the UTF-8 character set. |
| hash | yes | String(32) | HMAC MD5 hash (see hash generation) |
example
curl -d "merchantId=1234567" \
-d "projectId=1234" \
-d "merchantTxId=1234567890" \
-d "amount=100" \
-d "currency=EUR" \
-d "purpose=Beispieltransaktion" \
-d "bic=HYPTAT22" \
-d "urlRedirect=http://www.my-domain.de/girocheckout/redirect" \
-d "urlNotify=http://www.my-domain.de/girocheckout/notify" \
-d "hash=0399f30dab1a1c296703bb571a790fb2" \
https://payment.girosolution.de/girocheckout/api/v2/transaction/start
reply
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.
Parameter
| name | mandatory | type | description |
|---|---|---|---|
| rc | yes | Integer | response code |
| msg | yes | String(255) | additional information about the response code |
| reference | optional | String(36) | unique GiroCheckout transaction ID |
| redirect | optional | String(2048) | redirect URL to the buyer's online banking account |
| HEADER parameter | |||
| hash | yes | String(32) | HMAC MD5 hash overall the JSON string. (see api call reply) |
example in case of success
hash : b9d6a1e619ddb6a232274213885f5bb0
{"reference":"189d3a91-a760-4d3e-af7d-1fa7c57e1d2e","redirect":"https:\/\/www.banking.co.at\/appl\/ebp-vorproduktion\/logout\/so\/loginPrepare\/eps.html?resource=2\u0026cai=%2Bj8PpBHwCEBITWwYdtds2zIMtbNm7jfX4DOX1AQA1HdJ-","rc":"0","msg":""}
example in case of error
hash : 98d9d8b133acf97eb92601fa72d804a0
{"reference":"f84e606f-817d-439f-ada1-d37e85cb6314","redirect":"","rc":"5100","msg":""}
notification about the payment result
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 an eps payment is contained in the field gcResultPayment.
Due to the internal eps process, a redirection of the customer to urlRedirect is not done automatically but only after a customer click.
request
URL: notifyUrl of the prior init transaction call
provided by: merchant
called by: GiroCheckout
GET parameter
| name | mandatory | type | description |
|---|---|---|---|
| gcReference | yes | String(36) | unique GiroCheckout transaction ID |
| gcMerchantTxId | yes | String(255) | merchant transaction ID |
| gcBackendTxId | yes | String(10) | payment processor transaction ID |
| gcAmount | yes | Integer | if a decimal currency is used, the amount has to be in the smallest unit of value, eg. cent, penny |
| gcCurrency | yes | String(3) | currency |
| gcResultPayment | yes | Integer | payment result codes |
| gcHash | yes | String(32) | HMAC MD5 hash (see hash generation) |
reply
As a reply to the GET request, one of the following HTTP status codes is expected.
| HTTP status code | description |
|---|---|
| 200 (OK) | The notification was processed correctly. |
| 400 (Bad Request) | The merchant did not process the notification and does not wish to be notified again. |
| all others | The notification is repeated no more than 10 times every 30 minutes until the merchant returns the status code 200 or 400. |
redirection of the customer to merchant
After completing the payment, the customer may return to the merchant through a link. This return is not done automatically.
request
URL: redirectUrl of the prior init transaction call
provided by: merchant
called by: GiroCheckout
GET parameter
| name | mandatory | type | description |
|---|---|---|---|
| gcReference | yes | String(36) | unique GiroCheckout transaction ID |
| gcMerchantTxId | yes | String(255) | merchant transaction ID |
| gcBackendTxId | yes | String(10) | payment processor transaction ID |
| gcAmount | yes | Integer | if a decimal currency is used, the amount has to be in the smallest unit of value, eg. cent, penny |
| gcCurrency | yes | String(3) | currency |
| gcResultPayment | yes | Integer | payment result codes |
| gcHash | yes | String(32) | HMAC MD5 hash (see hash generation) |
Retrieve sender information
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.
API call
URL: https://payment.girosolution.de/girocheckout/api/v2/eps/senderinfo
Provided by: GiroCheckout
Called by: Merchant
POST Parameters
| Name | Mandatory | Type | Description |
|---|---|---|---|
| merchantId | Yes | Integer | merchant ID of a eps project |
| projectId | Yes | Integer | project ID of a eps project |
| reference | Yes | String(36) | GiroCheckout transaction ID |
| hash | Yes | String(32) | HMAC MD5 hash of the full JSON string. (see api call reply) |
Example
curl -d "merchantId=1234567" \
-d "projectId=1234" \
-d "reference=9ce6c641-4082-4f75-ae54-333309febcc5" \
-d "hash=246d1fa2ed97ecff895de974c560f9ec" \
https://payment.girosolution.de/girocheckout/api/v2/eps/senderinfo
Response
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.
JSON Parameters
| Name | Mandatory | Type | Description |
|---|---|---|---|
| rc | yes | Integer | response code |
| msg | yes | String(255) | additional information about the response code in case of error |
| accountholder | Optional | String(255) | Account holder of the sender account |
| iban | Optional | String(36) | IBAN of the sender account |
| bic | Optional | String(11) | BIC of the sender account |
| HEADER parameter | |||
| hash | yes | String(32) | HMAC MD5 hash of the full JSON string. (see api call reply) |
Example in case of success
hash : cde71b6b98e8dae709fdc1e17aef885f
{"accountholder":"Max Mustermann","iban":"DE87123456781234567890","bic":"TESTDETT421","rc":0,"msg":""}
Example in case of error
hash : f1d186103b8c4cb59c54ae7b987a9d4c
{"accountholder":null,"iban":null,"bic":null,"rc":5034,"msg":"Transaktion nicht vorhanden"}
en/girocheckout/eps/start.txt · Last modified: 2023/05/05 03:29