Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.<\/p>\n
Include giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.<\/p>\n
We provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos<\/a>.<\/p>\n<\/div><\/div>\nIf you are using the \/paymentMethods<\/a> to show available payment methods to the shopper, specify the following:<\/p>\n\n countryCode<\/a>: DE<\/strong><\/span><\/li>\n amount.currency<\/a>: EUR<\/strong><\/span><\/li>\n<\/ul>\nThe response contains paymentMethod.type<\/code>: giropay<\/strong><\/span>.<\/p>\nMake a payment<\/h2>\nIn your \/payments<\/a> request, specify:<\/p>\n\npaymentMethod.type<\/code>: giropay<\/strong><\/span><\/li>\n returnUrl<\/a>: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.<\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
If you are using the \/paymentMethods<\/a> to show available payment methods to the shopper, specify the following:<\/p>\n\n countryCode<\/a>: DE<\/strong><\/span><\/li>\n amount.currency<\/a>: EUR<\/strong><\/span><\/li>\n<\/ul>\nThe response contains paymentMethod.type<\/code>: giropay<\/strong><\/span>.<\/p>\nMake a payment<\/h2>\nIn your \/payments<\/a> request, specify:<\/p>\n\npaymentMethod.type<\/code>: giropay<\/strong><\/span><\/li>\n returnUrl<\/a>: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.<\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
The response contains paymentMethod.type<\/code>: giropay<\/strong><\/span>.<\/p>\nMake a payment<\/h2>\nIn your \/payments<\/a> request, specify:<\/p>\n\npaymentMethod.type<\/code>: giropay<\/strong><\/span><\/li>\n returnUrl<\/a>: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.<\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
paymentMethod.type<\/code>: giropay<\/strong><\/span>.<\/p>\nMake a payment<\/h2>\nIn your \/payments<\/a> request, specify:<\/p>\n\npaymentMethod.type<\/code>: giropay<\/strong><\/span><\/li>\n returnUrl<\/a>: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.<\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
In your \/payments<\/a> request, specify:<\/p>\n\npaymentMethod.type<\/code>: giropay<\/strong><\/span><\/li>\n returnUrl<\/a>: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.<\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
paymentMethod.type<\/code>: giropay<\/strong><\/span><\/li>\n returnUrl<\/a>: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.<\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
In the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
To complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
When using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
Redirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
After the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
details<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
In the response note the following:<\/p>\n
resultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
pspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
Use the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
<\/p>\n
The resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
resultCode<\/code> values you can receive for giropay are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper cancelled the payment while on their bank's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details<\/strong>\u00a0page in your\u00a0Customer Area<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful, and proceed with the order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nWe support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
If the shopper failed to return to your website or app, wait for the AUTHORISATION webhook<\/a> to receive the outcome of the payment:<\/p>\n
We support recurring transactions for giropay through SEPA Direct Debit<\/a>. To make recurring payments, you need to:<\/p>\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nStore SEPA details<\/h4>\nWhen creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
When creating a token<\/a> for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nWhen a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
When a token is created, you receive a recurring.token.created<\/a> webhook. The webhook contains the storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
storedPaymentMethodId<\/code> that you can use to make subsequent payments using the stored payment details.<\/p>\nMake a payment with a token<\/h3>\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
Only use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
UnscheduledCardOnFile<\/code> and Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
Subscription<\/code> payments.<\/p>\n<\/div>\nMake a subscription payment<\/h4>\nMake a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
Make a subscription payment<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\nMake an unscheduled card-on-file payment<\/h4>\nMake an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
Make an unscheduled card-on-file<\/a> using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.<\/p>\n\n <\/code-sample>\n<\/div>\n\n <\/code-sample>\n<\/div>\nIf the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
If the payment was successfully received the response will contain a Received<\/strong> resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
resultCode<\/code> and a pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
pspReference<\/code>, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.<\/p>\nTest and go live<\/h2>\nOn the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
On the bank selection screen, select giropay Testbank<\/strong>. You can use the following details to make test payments:<\/p>\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\nYou can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
IBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456<\/p>\n
You can check the status of a giropay test payment in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\n <\/p>\nBefore you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
Before you can accept live giropay payments, you need to submit a request for giropay<\/a> in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API-only integration guide\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n Tokenization for recurring payments\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","articleFields":{"description":"Add giropay to an existing API-only integration.","parameters":{"integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20only","payment_method_type":"giropay","payment_methoe":"giropay"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/giropay\/api-only","title":"giropay for API only","content":"Accept giropay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add in your test Customer Area.\n\n\n\nBuild your payment form for giropay\nInclude giropay in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.\n\nWe provide a giropay logo which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: DE\n amount.currency: EUR\n\nThe response contains paymentMethod.type: giropay.\nMake a payment\nIn your \/payments request, specify:\n\npaymentMethod.type: giropay\n returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for giropay are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 2-3 days.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method. For a description of the refusal reason, check the\u00a0Payment Details\u00a0page in your\u00a0Customer Area.\n\n\n\nIf the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful, and proceed with the order.\n\n\n\nRecurring payments\nWe support recurring transactions for giropay through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nStore SEPA details\nWhen creating a token for SEPA Direct Debit, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. You do not need to include any additional parameters for SEPA Direct Debit.\n\n \n\n\n \n\nIf the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.\nTest and go live\nOn the bank selection screen, select giropay Testbank. You can use the following details to make test payments:\nIBAN: DE48499999601234567890\nVR-NetKey: Any value allowed\nPIN: 1234\nTAN (for Photo and Flicker devices): 123456\nYou can check the status of a giropay test payment in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\n \nBefore you can accept live giropay payments, you need to submit a request for giropay in your live Customer Area.\nSee also\n\n\n API-only integration guide\n \n Webhooks\n \n Tokenization for recurring payments\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"giropay","lvl3":"giropay for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/giropay","lvl3":"\/payment-methods\/giropay\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["giropay"]},"articleFiles":{"giropay-payments.js":"giropay-payments.js<\/p>"}}
giropay-payments.js<\/p>"}}