Adyen APIs Postman collections<\/h5>![\"\"](\"\/user\/pages\/reuse\/pfs-general\/link-to-postman-collections\/postman-icon.svg?decoding=auto&fetchpriority=auto\")
Fork our Postman collections<\/a> in your private workspace to start testing API calls with your own credentials.<\/p><\/div><\/div>\n\nBefore you start building your integration, make sure that you have already:<\/p>\n
\n- Designed your implementation<\/a>.<\/li>\n
- Received your Issuing test account and API credential<\/a> from your Adyen contact.<\/li>\n<\/ul>\n
Verify your test credentials<\/h2>\n
To verify that your test API credentials are working, make your first requests.<\/p>\n
You need the API keys of the following credentials to make these requests:<\/p>\n
\n- ws_[123456]@BalancePlatform.[YourBalancePlatform]<\/strong><\/span>: use this API key to make requests to the Configuration API<\/a> and the Transfers API<\/a>.<\/li>\n
- ws_[123456]@Scope.Company_[YourCompanyAccount]<\/strong><\/span>: use this API key to make requests to the Legal Entity Management API<\/a>.<\/li>\n<\/ul>\n
Try out the requests below.<\/p>\n\n
\n \n \n <\/tabs>\n <\/div>\n<\/div>\n\nOnboard legal entities<\/h2>\n
Before you can start issuing cards, your account holders need to go through verification checks. Adyen performs the checks against the legal entity of the account holder.<\/p>\n
\n- Identify the required information<\/strong>.
\nCheck the required information<\/a> based on the location where the account holder is operating in.<\/li>\n- Create legal entities<\/strong>.
\nCreate a legal entity resource<\/a> for the account holder's organization and for the individuals associated to the organization.<\/li>\n- Add transfer instruments<\/strong>.
\nFor use cases that involve moving funds between balance accounts and bank accounts, add a transfer instrument<\/a> to represent the account holder's bank account.<\/li>\n- Upload additional documents<\/strong>.
\nAdyen may also require you to upload additional documents<\/a> if needed.<\/li>\n<\/ol>\nCreate account holders and balance accounts<\/h2>\n
Create an account holder and one or more balance accounts.<\/p>\n
\n- Create account holders<\/strong>.
\nCreate an account holder<\/a> and link it to their legal entity.<\/li>\n- Create balance accounts<\/strong>.
\nCreate balance accounts<\/a> and link the accounts to the account holder(s).<\/li>\n<\/ol>\nManage your platform<\/h2>\n
Learn how to update manage account holders and balance accounts to view details or update statuses.<\/p>\n
\n- Manage account holders<\/strong>.
\nView<\/a> and update<\/a> account holders in your platform.<\/li>\n- Manage balance accounts<\/strong>.
\nView<\/a> and update<\/a> balance accounts in your platform.<\/li>\n<\/ul>\nCreate cards<\/h2>\n
Create virtual or physical cards<\/a> depending on your use case.<\/p>\nWhen you successfully create virtual cards in the test environment, you receive the card number, expiry date, and CVC. You use these card details to make a test payment.<\/p>\n
Manage card status<\/h2>\n
Depending on your use case, you can change a card's status.<\/p>\n
\n- \n
Suspend a single-use card after it has been used.<\/strong>
\nIf a single-use card has been used, suspend the card<\/a> to temporarily prevent payments.<\/p>\n<\/li>\n- \n
Close a card.<\/strong>
\nIf a card should no longer be used, close the card<\/a>. Closing a card is a permanent action and cannot be reversed.<\/p>\n<\/li>\n<\/ul>\nAdd and manage funds<\/h2>\n
To make test payments with an Adyen-issued card, you need to make sure the balance accounts have funds.<\/p>\n
\n- Add funds to your liable balance account<\/strong>.
\nReach out to your Adyen contact to help you add funds to your liable balance account<\/a> in the test environment.<\/li>\n<\/ul>\nWhen you have the funds on your liable balance account, you can then:<\/p>\n
\n- Manage funds<\/strong>.
\nTransfer funds<\/a> to other balance accounts. The flow of funds between the liable balance account and other balance accounts depends your business logic and on how you designed your account structure.<\/li>\n<\/ul>\nApprove or decline payments<\/h2>\n
With relayed authorisation<\/a>, you approve or decline a payment by responding to a webhook. With transaction rules<\/a>, payments are approved or declined based on conditions. You can use relayed authorisation, transaction rules, or both.<\/p>\nWhen combined, transaction rules are applied first, serving as a filtering mechanism for payment attempts before sending you the relayed authorisation webhook.<\/p>\n
Use relayed authorisation<\/h3>\n
If you decide to use relayed authorisation to approve or decline payments within 2000 milliseconds of the payment attempt, you have to:<\/p>\n
\n- Expose an endpoint to handle relayed authorisation webhooks<\/strong>.
\nConfigure an endpoint to receive relayed authorisation<\/a> webhooks. To differentiate relayed authorisation webhooks from webhooks for other platform events, make sure this a separate endpoint from your webhooks<\/a>.<\/li>\n- Configure the relayed authorisation webhook in Adyen<\/strong>.<\/li>\n
- Respond to relayed authorisation webhooks<\/strong>.
\nRespond to the webhook within 2000 milliseconds of the payment attempt, specifying if you want to allow or decline<\/a> the payment.
You can define default fallback logic for Adyen to apply to the payment attempt in cases when Adyen does not receive a response, or receives an invalid response, from you.<\/li>\n<\/ol>\nUse transaction rules<\/h3>\n
Before you start creating transaction rules, make sure that you have already clearly defined your business logic and requirements when approving or declining payments. You turn these requirements into rule conditions.<\/p>\n
\n- Create payment instrument groups<\/strong>.
\nGrouping together payment instruments is useful if you want to apply a transaction rule to multiple cards. Create a payment instrument group<\/a>, assign cards to the group, and assign a transaction rule to the group.<\/li>\n- Create transaction rules<\/strong>.
\nDefine rule conditions<\/a>. A payment is automatically approved or declined depending on the conditions in the transaction rule. A transaction rule must be linked to one payment instrument, payment instrument group, or the whole balance platform.<\/li>\n<\/ol>\nMake test payments<\/h2>\n
Ask your Adyen contact for your online payments API credential. This API credential is different from the one that you use with the Balance Platform or Legal Entity Management APIs.<\/p>\n
You use your online payments API credentials to simulate payments in the test environment using the \/payments<\/a> endpoint.<\/p>\nFor example, to make a EUR 10<\/strong> payment, replace the number<\/code>, expiryMonth<\/code>, expiryYear<\/code>, and cvc<\/code> with the card details you received when you created the card<\/a>.<\/p>\n\n <\/code-sample>\n<\/div>\nThe response depends on whether you approved or declined the payment<\/a>.<\/p>\nProcess webhooks<\/h2>\n
Adyen sends webhooks to communicate asynchronous events in your platform such as payments, captures, refunds, and fund transfers.<\/p>\n
\n- Configure a webhook endpoint on your server<\/strong>.
\nSet up a webhook endpoint<\/a> in your system to receive webhooks from Adyen. If you are also accepting relayed authorisation webhooks<\/a>, make sure to use separate endpoints.<\/li>\n- Configure the endpoint in Adyen<\/strong>.\n
\n- Configure regular webhooks<\/a><\/li>\n
- Configure relayed authorisation webhooks<\/a><\/li>\n<\/ul><\/li>\n
- Receive and accept webhooks<\/strong>.
\nAccept and process<\/a> different webhook types.<\/li>\n<\/ol>\nDownload reports<\/h2>\n
You can use reports to reconcile payments and balances in your system.<\/p>\n
\n- Set up your reports credentials<\/strong>.
\nYour Adyen contact will provide you with a reports credential, which you need if you want to programmatically download reports.<\/li>\n- Download reports<\/strong>.
\nListen to the balancePlatform.report.created<\/a> webhook to know when a report was generated and is ready to be downloaded. To download a report, you must authenticate your GET requests with your report credentials.<\/li>\n<\/ol>\nGoing live<\/h2>\n
To start issuing cards in the live environment, you need to apply for a live account<\/a>. When you have your live account, follow the steps below to take your integration live.<\/p>\n\n- \n
Replicate your test account setup<\/strong>.<\/p>\nThe setup from your test Adyen Issuing account is not<\/em> replicated to your live Adyen Issuing account. If you created the following resources in your test environment, make sure that you replicate your setup in your live account:<\/p>\n\n- Account holders<\/a><\/li>\n
- Balance accounts<\/a><\/li>\n
- Transaction rules<\/a><\/li>\n
- Payment instrument groups<\/a>
\n
<\/li>\n<\/ul>\n<\/li>\n- \n
Update your code base<\/strong>.
\nUpdate your code base and Issuing account settings.<\/p>\n\n- \n
Switch to live Balance Platform and Legal Entity Management API credentials<\/strong>.
\nGet your live API credentials from your Adyen contact. Copy these keys to your live platform.<\/p>\n<\/li>\n- \n
Switch from test to live endpoints<\/strong>.
\nChange the test endpoint https:\/\/balanceplatform-api-test.adyen.com\/<\/code> to live
\nhttps:\/\/balanceplatform-api-live.adyen.com\/<\/code>.
\n
<\/p>\n<\/li>\n<\/ol>\n<\/li>\n- \n
Run end-to-end tests<\/strong>.<\/p>\n\n- Live Balance Platform and Legal Entity Management API credentials: Make your first live API request<\/a> to make sure that your live API credentials are working.<\/li>\n
- Account holders<\/a> and balance accounts<\/a>: Confirm you can create and retrieve account holders and balance accounts.<\/li>\n
- Cards<\/a>: Confirm that you can create cards.<\/li>\n
- Transaction rules<\/a>: Confirm that you can create and manage transaction rules.<\/li>\n
- Relayed authorisation<\/a>: Confirm that you can receive relayed authorisation webhooks, and that you can successfully respond to approve or decline payments.<\/li>\n
- Payments:\n
\n- Test the happy flow by making payments with cards you created in the live environment.<\/li>\n
- Test non-happy payment flows where payments are declined through relayed authorisation or transaction rules.<\/li>\n<\/ul><\/li>\n
- Webhooks<\/a>: Confirm that you can receive and accept webhooks in the live environment.<\/li>\n
- Verification errors<\/a>: Test your error handling scenarios when onboarding users.<\/li>\n
- Reports<\/a>: Confirm that you can download reports for transactions in the live environment.<\/li>\n<\/ul>\n<\/li>\n<\/ol>","url":"https:\/\/docs.adyen.com\/pt\/issuing\/integration-checklist","articleFields":{"description":"Checklist for building and taking your Issuing integration live.","feedback_component":true,"last_edit_on":"22-10-2021 09:36","cache_enable":false,"page_id":"c53bfadf-de3d-45d8-8cee-2568786bac29","filters_component":false,"decision_tree":"[]","parameters":{"directoryPath":"\/issuing"}},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/issuing\/integration-checklist","title":"Integration and go-live checklist","content":"On this page you learn the steps for developing an Adyen Issuing integration and for taking your integration live.\n\nAdyen APIs Postman collections Fork our Postman collections in your private workspace to start testing API calls with your own credentials.\n\nBefore you start building your integration, make sure that you have already:\n\nDesigned your implementation.\nReceived your Issuing test account and API credential from your Adyen contact.\n\nVerify your test credentials\nTo verify that your test API credentials are working, make your first requests.\nYou need the API keys of the following credentials to make these requests:\n\nws_[123456]@BalancePlatform.[YourBalancePlatform]: use this API key to make requests to the Configuration API and the Transfers API.\nws_[123456]@Scope.Company_[YourCompanyAccount]: use this API key to make requests to the Legal Entity Management API.\n\nTry out the requests below.\n\n\n \n \n \n \n\n\nOnboard legal entities\nBefore you can start issuing cards, your account holders need to go through verification checks. Adyen performs the checks against the legal entity of the account holder.\n\nIdentify the required information.\nCheck the required information based on the location where the account holder is operating in.\nCreate legal entities.\nCreate a legal entity resource for the account holder's organization and for the individuals associated to the organization.\nAdd transfer instruments.\nFor use cases that involve moving funds between balance accounts and bank accounts, add a transfer instrument to represent the account holder's bank account.\nUpload additional documents.\nAdyen may also require you to upload additional documents if needed.\n\nCreate account holders and balance accounts\nCreate an account holder and one or more balance accounts.\n\nCreate account holders.\nCreate an account holder and link it to their legal entity.\nCreate balance accounts.\nCreate balance accounts and link the accounts to the account holder(s).\n\nManage your platform\nLearn how to update manage account holders and balance accounts to view details or update statuses.\n\nManage account holders.\nView and update account holders in your platform.\nManage balance accounts.\nView and update balance accounts in your platform.\n\nCreate cards\nCreate virtual or physical cards depending on your use case.\nWhen you successfully create virtual cards in the test environment, you receive the card number, expiry date, and CVC. You use these card details to make a test payment.\nManage card status\nDepending on your use case, you can change a card's status.\n\n\nSuspend a single-use card after it has been used.\nIf a single-use card has been used, suspend the card to temporarily prevent payments.\n\n\nClose a card.\nIf a card should no longer be used, close the card. Closing a card is a permanent action and cannot be reversed.\n\n\nAdd and manage funds\nTo make test payments with an Adyen-issued card, you need to make sure the balance accounts have funds.\n\nAdd funds to your liable balance account.\nReach out to your Adyen contact to help you add funds to your liable balance account in the test environment.\n\nWhen you have the funds on your liable balance account, you can then:\n\nManage funds.\nTransfer funds to other balance accounts. The flow of funds between the liable balance account and other balance accounts depends your business logic and on how you designed your account structure.\n\nApprove or decline payments\nWith relayed authorisation, you approve or decline a payment by responding to a webhook. With transaction rules, payments are approved or declined based on conditions. You can use relayed authorisation, transaction rules, or both.\nWhen combined, transaction rules are applied first, serving as a filtering mechanism for payment attempts before sending you the relayed authorisation webhook.\nUse relayed authorisation\nIf you decide to use relayed authorisation to approve or decline payments within 2000 milliseconds of the payment attempt, you have to:\n\nExpose an endpoint to handle relayed authorisation webhooks.\nConfigure an endpoint to receive relayed authorisation webhooks. To differentiate relayed authorisation webhooks from webhooks for other platform events, make sure this a separate endpoint from your webhooks.\nConfigure the relayed authorisation webhook in Adyen.\nRespond to relayed authorisation webhooks.\nRespond to the webhook within 2000 milliseconds of the payment attempt, specifying if you want to allow or decline the payment.You can define default fallback logic for Adyen to apply to the payment attempt in cases when Adyen does not receive a response, or receives an invalid response, from you.\n\nUse transaction rules\nBefore you start creating transaction rules, make sure that you have already clearly defined your business logic and requirements when approving or declining payments. You turn these requirements into rule conditions.\n\nCreate payment instrument groups.\nGrouping together payment instruments is useful if you want to apply a transaction rule to multiple cards. Create a payment instrument group, assign cards to the group, and assign a transaction rule to the group.\nCreate transaction rules.\nDefine rule conditions. A payment is automatically approved or declined depending on the conditions in the transaction rule. A transaction rule must be linked to one payment instrument, payment instrument group, or the whole balance platform.\n\nMake test payments\nAsk your Adyen contact for your online payments API credential. This API credential is different from the one that you use with the Balance Platform or Legal Entity Management APIs.\nYou use your online payments API credentials to simulate payments in the test environment using the \/payments endpoint.\nFor example, to make a EUR 10 payment, replace the number, expiryMonth, expiryYear, and cvc with the card details you received when you created the card.\n\n \n\nThe response depends on whether you approved or declined the payment.\nProcess webhooks\nAdyen sends webhooks to communicate asynchronous events in your platform such as payments, captures, refunds, and fund transfers.\n\nConfigure a webhook endpoint on your server.\nSet up a webhook endpoint in your system to receive webhooks from Adyen. If you are also accepting relayed authorisation webhooks, make sure to use separate endpoints.\nConfigure the endpoint in Adyen.\n\nConfigure regular webhooks\nConfigure relayed authorisation webhooks\n\nReceive and accept webhooks.\nAccept and process different webhook types.\n\nDownload reports\nYou can use reports to reconcile payments and balances in your system.\n\nSet up your reports credentials.\nYour Adyen contact will provide you with a reports credential, which you need if you want to programmatically download reports.\nDownload reports.\nListen to the balancePlatform.report.created webhook to know when a report was generated and is ready to be downloaded. To download a report, you must authenticate your GET requests with your report credentials.\n\nGoing live\nTo start issuing cards in the live environment, you need to apply for a live account. When you have your live account, follow the steps below to take your integration live.\n\n\nReplicate your test account setup.\nThe setup from your test Adyen Issuing account is not replicated to your live Adyen Issuing account. If you created the following resources in your test environment, make sure that you replicate your setup in your live account:\n\nAccount holders\nBalance accounts\nTransaction rules\nPayment instrument groups\n\n\n\n\nUpdate your code base.\nUpdate your code base and Issuing account settings.\n\n\nSwitch to live Balance Platform and Legal Entity Management API credentials.\nGet your live API credentials from your Adyen contact. Copy these keys to your live platform.\n\n\nSwitch from test to live endpoints.\nChange the test endpoint https:\/\/balanceplatform-api-test.adyen.com\/ to live\nhttps:\/\/balanceplatform-api-live.adyen.com\/.\n\n\n\n\n\nRun end-to-end tests.\n\nLive Balance Platform and Legal Entity Management API credentials: Make your first live API request to make sure that your live API credentials are working.\nAccount holders and balance accounts: Confirm you can create and retrieve account holders and balance accounts.\nCards: Confirm that you can create cards.\nTransaction rules: Confirm that you can create and manage transaction rules.\nRelayed authorisation: Confirm that you can receive relayed authorisation webhooks, and that you can successfully respond to approve or decline payments.\nPayments:\n\nTest the happy flow by making payments with cards you created in the live environment.\nTest non-happy payment flows where payments are declined through relayed authorisation or transaction rules.\n\nWebhooks: Confirm that you can receive and accept webhooks in the live environment.\nVerification errors: Test your error handling scenarios when onboarding users.\nReports: Confirm that you can download reports for transactions in the live environment.\n\n\n","type":"page","locale":"pt","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Adyen Issuing","lvl2":"Integration and go-live checklist"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/issuing","lvl2":"\/pt\/issuing\/integration-checklist"},"levels":3,"category":"Issuing","category_color":"green","tags":["Integration","go-live","checklist"]},"articleFiles":{"create-legalentity-request.js":"
create-legalentity-request.js<\/p>","create-payment-request.js":"
create-payment-request.js<\/p>","get-balanceplatform-request.js":"
get-balanceplatform-request.js<\/p>"}}
Before you start building your integration, make sure that you have already:<\/p>\n To verify that your test API credentials are working, make your first requests.<\/p>\n You need the API keys of the following credentials to make these requests:<\/p>\n Try out the requests below.<\/p>\n\n Before you can start issuing cards, your account holders need to go through verification checks. Adyen performs the checks against the legal entity of the account holder.<\/p>\n Create an account holder and one or more balance accounts.<\/p>\n Learn how to update manage account holders and balance accounts to view details or update statuses.<\/p>\n Create virtual or physical cards<\/a> depending on your use case.<\/p>\n When you successfully create virtual cards in the test environment, you receive the card number, expiry date, and CVC. You use these card details to make a test payment.<\/p>\n Depending on your use case, you can change a card's status.<\/p>\n Suspend a single-use card after it has been used.<\/strong> Close a card.<\/strong> To make test payments with an Adyen-issued card, you need to make sure the balance accounts have funds.<\/p>\n When you have the funds on your liable balance account, you can then:<\/p>\n With relayed authorisation<\/a>, you approve or decline a payment by responding to a webhook. With transaction rules<\/a>, payments are approved or declined based on conditions. You can use relayed authorisation, transaction rules, or both.<\/p>\n When combined, transaction rules are applied first, serving as a filtering mechanism for payment attempts before sending you the relayed authorisation webhook.<\/p>\n If you decide to use relayed authorisation to approve or decline payments within 2000 milliseconds of the payment attempt, you have to:<\/p>\n Before you start creating transaction rules, make sure that you have already clearly defined your business logic and requirements when approving or declining payments. You turn these requirements into rule conditions.<\/p>\n Ask your Adyen contact for your online payments API credential. This API credential is different from the one that you use with the Balance Platform or Legal Entity Management APIs.<\/p>\n You use your online payments API credentials to simulate payments in the test environment using the \/payments<\/a> endpoint.<\/p>\n For example, to make a EUR 10<\/strong> payment, replace the The response depends on whether you approved or declined the payment<\/a>.<\/p>\n Adyen sends webhooks to communicate asynchronous events in your platform such as payments, captures, refunds, and fund transfers.<\/p>\n You can use reports to reconcile payments and balances in your system.<\/p>\n To start issuing cards in the live environment, you need to apply for a live account<\/a>. When you have your live account, follow the steps below to take your integration live.<\/p>\n Replicate your test account setup<\/strong>.<\/p>\n The setup from your test Adyen Issuing account is not<\/em> replicated to your live Adyen Issuing account. If you created the following resources in your test environment, make sure that you replicate your setup in your live account:<\/p>\n Update your code base<\/strong>. Switch to live Balance Platform and Legal Entity Management API credentials<\/strong>. Switch from test to live endpoints<\/strong>. Run end-to-end tests<\/strong>.<\/p>\n create-legalentity-request.js<\/p>","create-payment-request.js":" create-payment-request.js<\/p>","get-balanceplatform-request.js":" get-balanceplatform-request.js<\/p>"}}
Fork our Postman collections<\/a> in your private workspace to start testing API calls with your own credentials.<\/p><\/div><\/div>\n\n\n
Verify your test credentials<\/h2>\n
\n
Onboard legal entities<\/h2>\n
\n
\nCheck the required information<\/a> based on the location where the account holder is operating in.<\/li>\n
\nCreate a legal entity resource<\/a> for the account holder's organization and for the individuals associated to the organization.<\/li>\n
\nFor use cases that involve moving funds between balance accounts and bank accounts, add a transfer instrument<\/a> to represent the account holder's bank account.<\/li>\n
\nAdyen may also require you to upload additional documents<\/a> if needed.<\/li>\n<\/ol>\nCreate account holders and balance accounts<\/h2>\n
\n
\nCreate an account holder<\/a> and link it to their legal entity.<\/li>\n
\nCreate balance accounts<\/a> and link the accounts to the account holder(s).<\/li>\n<\/ol>\nManage your platform<\/h2>\n
\n
\nView<\/a> and update<\/a> account holders in your platform.<\/li>\n
\nView<\/a> and update<\/a> balance accounts in your platform.<\/li>\n<\/ul>\nCreate cards<\/h2>\n
Manage card status<\/h2>\n
\n
\nIf a single-use card has been used, suspend the card<\/a> to temporarily prevent payments.<\/p>\n<\/li>\n
\nIf a card should no longer be used, close the card<\/a>. Closing a card is a permanent action and cannot be reversed.<\/p>\n<\/li>\n<\/ul>\nAdd and manage funds<\/h2>\n
\n
\nReach out to your Adyen contact to help you add funds to your liable balance account<\/a> in the test environment.<\/li>\n<\/ul>\n\n
\nTransfer funds<\/a> to other balance accounts. The flow of funds between the liable balance account and other balance accounts depends your business logic and on how you designed your account structure.<\/li>\n<\/ul>\nApprove or decline payments<\/h2>\n
Use relayed authorisation<\/h3>\n
\n
\nConfigure an endpoint to receive relayed authorisation<\/a> webhooks. To differentiate relayed authorisation webhooks from webhooks for other platform events, make sure this a separate endpoint from your webhooks<\/a>.<\/li>\n
\nRespond to the webhook within 2000 milliseconds of the payment attempt, specifying if you want to allow or decline<\/a> the payment.
You can define default fallback logic for Adyen to apply to the payment attempt in cases when Adyen does not receive a response, or receives an invalid response, from you.<\/li>\n<\/ol>\nUse transaction rules<\/h3>\n
\n
\nGrouping together payment instruments is useful if you want to apply a transaction rule to multiple cards. Create a payment instrument group<\/a>, assign cards to the group, and assign a transaction rule to the group.<\/li>\n
\nDefine rule conditions<\/a>. A payment is automatically approved or declined depending on the conditions in the transaction rule. A transaction rule must be linked to one payment instrument, payment instrument group, or the whole balance platform.<\/li>\n<\/ol>\nMake test payments<\/h2>\n
number<\/code>, expiryMonth<\/code>, expiryYear<\/code>, and cvc<\/code> with the card details you received when you created the card<\/a>.<\/p>\nProcess webhooks<\/h2>\n
\n
\nSet up a webhook endpoint<\/a> in your system to receive webhooks from Adyen. If you are also accepting relayed authorisation webhooks<\/a>, make sure to use separate endpoints.<\/li>\n\n
\nAccept and process<\/a> different webhook types.<\/li>\n<\/ol>\nDownload reports<\/h2>\n
\n
\nYour Adyen contact will provide you with a reports credential, which you need if you want to programmatically download reports.<\/li>\n
\nListen to the balancePlatform.report.created<\/a> webhook to know when a report was generated and is ready to be downloaded. To download a report, you must authenticate your GET requests with your report credentials.<\/li>\n<\/ol>\nGoing live<\/h2>\n
\n
\n
\n
<\/li>\n<\/ul>\n<\/li>\n
\nUpdate your code base and Issuing account settings.<\/p>\n\n
\nGet your live API credentials from your Adyen contact. Copy these keys to your live platform.<\/p>\n<\/li>\n
\nChange the test endpoint https:\/\/balanceplatform-api-test.adyen.com\/<\/code> to live
\nhttps:\/\/balanceplatform-api-live.adyen.com\/<\/code>.
\n
<\/p>\n<\/li>\n<\/ol>\n<\/li>\n\n
\n