\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/pad\/web-component","articleFields":{"description":"Add Pre-Authorized Debit Canada (PADs Canada) to your Components integration.","never_cache_twig":true,"parameters":{"tx_variant":"eft_directdebit_CA","component_class_name":"preAuthorizedDebitCanada","component_class_lowercase":"preAuthorizedDebitCanada","integration":"Components","pm_directory":"eft_directdebit_CA","payment_method":"PADs Canada","action_type":"none"},"filters_component":true,"filters_config_folder":"payment-methods\/pad\/web\/component-web"},"algolia":[{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/pad\/web-component","title":"Pre-Authorized Debit Canada Web Component","content":"Requirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have an existing Sessions flow Web Components integration.\n\n\n\nCheckout API\nMake sure that you use Checkout API v69 or later.\n \n\n\nWebhooks\nSubscribe to DIRECT_DEBIT_NOTICE_OF_CHANGE_NOTIFICATION webhooks to receive a notification when a shopper has outdated banking details.\n\n\nSetup steps\nBefore you begin: Contact our Support Team to add PADs Canada in your Customer Area. Make sure you have a way to get a mandate (consent) from the shopper. \n\n\n\nImport PADs Canada\nWhen you import Adyen Web, include PreAuthorizedDebitCanada.\n\n \nAdd additional configuration for PADs Canada\nYou do not need to add any configuration parameters for PADs Canada.\nInitialize the Component for PADs Canada\nTo initialize PADs Canada, use the PreAuthorizedDebitCanada class.\n\n \n\nAdd additional parameters to your \/sessions request\nWhen you create a payment session, add the following parameters:\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\n billingAddress\n\nThe account owner's address information.\n\n\nTokenization parameters\n\nWe do not recommend using PADs for one-off payments. Follow the instructions in Create tokens to create a token with the shopper's initial payment, and then make a payment with the token in the subsequent recurring PADs. To create a token, add the tokenization parameters recurringProcessingModel, shopperInteraction, shopperReference, and storePaymentMethod.\n\n\n\nNote that you need to get a mandate (consent) from the shopper for the payment or series of recurring payments.\n\n \n\nGet the payment outcome\nYour Components integration gets the payment outcome, so you do not need to do anything additional.\nIf you created a token, you receive it as the storedPaymentMethodId in a recurring.token.created webhook. Save the token along with your shopper reference for use in future payments.\nIt can take up to five business days to know whether the payment was authorized by the bank. If the payment is successful, it will appear in the Settlement details report. If it fails, you may receive a CHARGEBACK.Recurring payments\nPre-Authorized Debit Canada supports tokenization of the shopper's payment details for recurring transactions. Due to the risk of chargebacks, we do not recommend using PADs for one-off payments.\n\nYou are required to obtain a mandate from the shopper if you intend to make future recurring payments.\n\nTo make recurring payments, refer to Tokenization to:\n\nEnable the Recurring tokens life cycle events webhook.\nCreate a token through the initial payment (see Add additional parameters above).\nPay with the token in subsequent payments. Note that you do not need to include the mandate ID in the recurring payment request.\nManage tokens.\nTest and go live\nYou can test Pre-Authorized Debit Canada payments as well as chargebacks.\nTest the payment flow\nTest your integration by making test payments using the bankAccountNumber, bankLocationId, bankCode and ownerName of a real Canadian bank account. That account will not be debited.\nYou can also use the following test credentials:\n\nAccount holder name: TEST\nAccount number: 00257596\nInstitution number: 002\nTransit number: 57596\n\nTest the chargeback flow\nYou can test the return flow by making test payments with an ownerName value that consists of chargeback: followed by a PAD return reason code. For example, chargeback:05. The other account details to use are the same as when testing payments.\nNote that in the test environment the return flow goes directly to the Chargeback stage.\nReturn reason codes\nUse the following table with the most common PAD return reason codes to determine what the code means and if it is allowed to retry a returned payment.\n\n \n\n\n\nReason code\nReason\nDescription \/ Resolution\nRetry?\n\n\n\n\n01\nNSF (Debit Only)\nNon-sufficient funds (NSF). You can retry the transaction once within 30 days of the original authorization date.\n max 1x\n\n\n02\nAccount not found\nThe provided account information is incorrect. Retrying the transaction is not allowed.\n\n\n\n03\nPayment Stopped\/Recalled\nThe customer instructed their bank to not honor a payment they previously authorized. Resolve the issue with the customer. When initiating a new transaction, get a new PAD agreement from the customer. If you are going to debit the same account, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n05\nAccount Closed\nThe customer's bank account has been closed. Retrying the transaction is not allowed.\n\n\n\n07\nNo Debit Allowed\nThe provided bank account cannot be used for EFT PADs. Ask the customer for permission to charge a different, EFT PAD-enabled bank account.\n\n\n\n08\nFunds Not Cleared (Debit Only)\nInsufficient funds. You can retry the transaction once within 30 days of the original authorization date.\n max 1x\n\n\n09\nCurrency\/Account Mismatch\nThe transaction currency does not match the currency of the bank account. Retrying the transaction is not allowed.\n\n\n\n10\nPayor\/Payee Deceased\nContact the bank of the deceased account holder or account beneficiary.\n\n\n\n11\nAccount Frozen\nContact your customer to obtain a different form of payment. The bank account cannot be used while it is frozen. This return code should be a red flag for your business. If you see this code, do your due diligence around verifying the identity of your customer.\n\n\n\n12\nInvalid\/Incorrect Account No.\nThe provided account number is incorrect. Retrying the transaction is not allowed.\n\n\n\n14\nIncorrect Payor\/Payee Name\nThe provided name of the account holder or beneficiary is incorrect. Retrying the transaction is not allowed.\n\n\n\n15\nNo Agreement Existed\nThe customer informed their bank they did not give authorization for the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n16\nNot According to Agreement - Personal\nThe customer informed their bank that the payment is not in accordance with their personal PAD agreement. Suspend any recurring transactions and resolve the issue with the customer.\n\n\n\n17\nAgreement Revoked - Personal\nThe customer informed their bank they revoked their personal PAD agreement for the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n18\nNo Confirmation\/Pre-Notification - Personal\nThe consumer you tried to charge informed their bank they did not receive a confirmation or notification about the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n19\nNot According to Agreement - Business\nThe customer informed their bank that the payment is not in accordance with their business PAD agreement. Suspend any recurring transactions and resolve the issue with the customer.\n\n\n\n20\nAgreement Revoked - Business\nThe customer informed their bank they revoked their business PAD agreement for the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n21\nNo Confirmation\/Pre-Notification - Business\nThe company you tried to charge informed their bank they did not receive a confirmation or notification about the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n82\nInterbank Reject - Invalid Institution Number\nThe bank's institution number and\/or branch transit number is invalid, or the bank does not accept PADs.\n\n\n\n90\nInstitution in Default\nThe customer's bank has failed to fulfill its obligations. Retrying the transaction is not allowed.\n\n\n\n\n\n\n\nGo live\nBefore going live, contact our Support Team to add PADs Canada in your live Customer Area.","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Pre-Authorized Debit Canada","lvl3":"Pre-Authorized Debit Canada Web Component"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/pad","lvl3":"\/pt\/payment-methods\/pad\/web-component"},"levels":4,"category":"Payment method","category_color":"green","tags":["Pre-Authorized","Debit","Canada","Component"]},{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/pad\/web-component?flow=Sessions flow&integration=Component","title":"Sessions flow Component","content":"Requirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have an existing Sessions flow Web Components integration.\n\n\n\nCheckout API\nMake sure that you use Checkout API v69 or later.\n \n\n\nWebhooks\nSubscribe to DIRECT_DEBIT_NOTICE_OF_CHANGE_NOTIFICATION webhooks to receive a notification when a shopper has outdated banking details.\n\n\nSetup steps\nBefore you begin: Contact our Support Team to add PADs Canada in your Customer Area. Make sure you have a way to get a mandate (consent) from the shopper. \n\n\n\nImport PADs Canada\nWhen you import Adyen Web, include PreAuthorizedDebitCanada.\n\n \nAdd additional configuration for PADs Canada\nYou do not need to add any configuration parameters for PADs Canada.\nInitialize the Component for PADs Canada\nTo initialize PADs Canada, use the PreAuthorizedDebitCanada class.\n\n \n\nAdd additional parameters to your \/sessions request\nWhen you create a payment session, add the following parameters:\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\n billingAddress\n\nThe account owner's address information.\n\n\nTokenization parameters\n\nWe do not recommend using PADs for one-off payments. Follow the instructions in Create tokens to create a token with the shopper's initial payment, and then make a payment with the token in the subsequent recurring PADs. To create a token, add the tokenization parameters recurringProcessingModel, shopperInteraction, shopperReference, and storePaymentMethod.\n\n\n\nNote that you need to get a mandate (consent) from the shopper for the payment or series of recurring payments.\n\n \n\nGet the payment outcome\nYour Components integration gets the payment outcome, so you do not need to do anything additional.\nIf you created a token, you receive it as the storedPaymentMethodId in a recurring.token.created webhook. Save the token along with your shopper reference for use in future payments.\nIt can take up to five business days to know whether the payment was authorized by the bank. If the payment is successful, it will appear in the Settlement details report. If it fails, you may receive a CHARGEBACK.Recurring payments\nPre-Authorized Debit Canada supports tokenization of the shopper's payment details for recurring transactions. Due to the risk of chargebacks, we do not recommend using PADs for one-off payments.\n\nYou are required to obtain a mandate from the shopper if you intend to make future recurring payments.\n\nTo make recurring payments, refer to Tokenization to:\n\nEnable the Recurring tokens life cycle events webhook.\nCreate a token through the initial payment (see Add additional parameters above).\nPay with the token in subsequent payments. Note that you do not need to include the mandate ID in the recurring payment request.\nManage tokens.\nTest and go live\nYou can test Pre-Authorized Debit Canada payments as well as chargebacks.\nTest the payment flow\nTest your integration by making test payments using the bankAccountNumber, bankLocationId, bankCode and ownerName of a real Canadian bank account. That account will not be debited.\nYou can also use the following test credentials:\n\nAccount holder name: TEST\nAccount number: 00257596\nInstitution number: 002\nTransit number: 57596\n\nTest the chargeback flow\nYou can test the return flow by making test payments with an ownerName value that consists of chargeback: followed by a PAD return reason code. For example, chargeback:05. The other account details to use are the same as when testing payments.\nNote that in the test environment the return flow goes directly to the Chargeback stage.\nReturn reason codes\nUse the following table with the most common PAD return reason codes to determine what the code means and if it is allowed to retry a returned payment.\n\n \n\n\n\nReason code\nReason\nDescription \/ Resolution\nRetry?\n\n\n\n\n01\nNSF (Debit Only)\nNon-sufficient funds (NSF). You can retry the transaction once within 30 days of the original authorization date.\n max 1x\n\n\n02\nAccount not found\nThe provided account information is incorrect. Retrying the transaction is not allowed.\n\n\n\n03\nPayment Stopped\/Recalled\nThe customer instructed their bank to not honor a payment they previously authorized. Resolve the issue with the customer. When initiating a new transaction, get a new PAD agreement from the customer. If you are going to debit the same account, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n05\nAccount Closed\nThe customer's bank account has been closed. Retrying the transaction is not allowed.\n\n\n\n07\nNo Debit Allowed\nThe provided bank account cannot be used for EFT PADs. Ask the customer for permission to charge a different, EFT PAD-enabled bank account.\n\n\n\n08\nFunds Not Cleared (Debit Only)\nInsufficient funds. You can retry the transaction once within 30 days of the original authorization date.\n max 1x\n\n\n09\nCurrency\/Account Mismatch\nThe transaction currency does not match the currency of the bank account. Retrying the transaction is not allowed.\n\n\n\n10\nPayor\/Payee Deceased\nContact the bank of the deceased account holder or account beneficiary.\n\n\n\n11\nAccount Frozen\nContact your customer to obtain a different form of payment. The bank account cannot be used while it is frozen. This return code should be a red flag for your business. If you see this code, do your due diligence around verifying the identity of your customer.\n\n\n\n12\nInvalid\/Incorrect Account No.\nThe provided account number is incorrect. Retrying the transaction is not allowed.\n\n\n\n14\nIncorrect Payor\/Payee Name\nThe provided name of the account holder or beneficiary is incorrect. Retrying the transaction is not allowed.\n\n\n\n15\nNo Agreement Existed\nThe customer informed their bank they did not give authorization for the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n16\nNot According to Agreement - Personal\nThe customer informed their bank that the payment is not in accordance with their personal PAD agreement. Suspend any recurring transactions and resolve the issue with the customer.\n\n\n\n17\nAgreement Revoked - Personal\nThe customer informed their bank they revoked their personal PAD agreement for the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n18\nNo Confirmation\/Pre-Notification - Personal\nThe consumer you tried to charge informed their bank they did not receive a confirmation or notification about the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n19\nNot According to Agreement - Business\nThe customer informed their bank that the payment is not in accordance with their business PAD agreement. Suspend any recurring transactions and resolve the issue with the customer.\n\n\n\n20\nAgreement Revoked - Business\nThe customer informed their bank they revoked their business PAD agreement for the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n21\nNo Confirmation\/Pre-Notification - Business\nThe company you tried to charge informed their bank they did not receive a confirmation or notification about the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n82\nInterbank Reject - Invalid Institution Number\nThe bank's institution number and\/or branch transit number is invalid, or the bank does not accept PADs.\n\n\n\n90\nInstitution in Default\nThe customer's bank has failed to fulfill its obligations. Retrying the transaction is not allowed.\n\n\n\n\n\n\n\nGo live\nBefore going live, contact our Support Team to add PADs Canada in your live Customer Area.","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Pre-Authorized Debit Canada","lvl3":"Pre-Authorized Debit Canada Web Component"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/pad","lvl3":"\/pt\/payment-methods\/pad\/web-component"},"levels":4,"category":"Payment method","category_color":"green","tags":["Sessions flow","Component"]},{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/pad\/web-component?flow=Advanced flow&integration=Component","title":"Advanced flow Component","content":"Requirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have an existing Advanced flow Web Components integration.\n\n\n\nCheckout API\nMake sure that you use Checkout API v69 or later.\n \n\n\nWebhooks\nSubscribe to DIRECT_DEBIT_NOTICE_OF_CHANGE_NOTIFICATION webhooks to receive a notification when a shopper has outdated banking details.\n\n\nSetup steps\nBefore you begin: Contact our Support Team to add PADs Canada in your Customer Area. Make sure you have a way to get a mandate (consent) from the shopper. \n\n\n\nImport PADs Canada\nWhen you import Adyen Web, include PreAuthorizedDebitCanada.\n\n \nAdd additional configuration for PADs Canada\nConfigure the Component with the following configuration object:\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\nenableStoreDetails v5.24.0 or later\n\nSet to true to show the checkbox for saving the payment details. The default is false.\n\n\n\n\n \n\nInitialize the Component for PADs Canada\nTo initialize PADs Canada, use the PreAuthorizedDebitCanada class.\n\n \n\nAdd additional parameters to your \/payments request\nWhen you make a payment, add the following parameters to the \/payments request:\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\npaymentMethod.type\n\neft_directdebit_CA\n\n\npaymentMethod.bankAccountNumber\n\nThe Canadian bank account number.\n\n\npaymentMethod.bankLocationId\n\nThe five-digit code that identifies the branch where the account was opened.\n\n\npaymentMethod.bankCode\n\nThe three-digit code that identifies the bank.\n\n\npaymentMethod.ownerName\n\nThe name on the bank account.\n\n\n billingAddress\n\nThe account owner's address information.\n\n\nTokenization parameters\n\nWe do not recommend using PADs for one-off payments. Follow the instructions in Create tokens to create a token with the shopper's initial payment, and then use that token in the subsequent recurring PADs. To create a token, add the tokenization parameters recurringProcessingModel, shopperInteraction, shopperReference, and storePaymentMethod.\n\n\n\nNote that you need to get a mandate (consent) from the shopper for the payment or series of recurring payments.\n\n \n\nIn the \/payments response, note the following:\n\n\nadditionalData: an object with the following details to save in your system.\n\neft_directdebit_CA.mandateId: the ID we generated for the shopper's PAD agreement.\neft_directdebit_CA.dateOfSignature: the date of the initial payment request, which is considered to be the date that the shopper accepted the PAD agreement.\ntokenization.storedPaymentMethodId: the token to use in subsequent recurring PADs.\ntokenization.shopperReference: your unique ID for the shopper, to use in subsequent recurring PADs.\n\n\nThe tokenization response parameters are only included if the payment request contained the parameters to create a token, and in your Customer Area under Developers > Additional data you enabled Recurring details.\n\n\n\n\n \n\nGet the payment outcome\nYour Components integration gets the payment outcome, so you do not need to do anything additional.\nIf you created a token, you receive it as the storedPaymentMethodId in a recurring.token.created webhook. Save the token along with your shopper reference for use in future payments.\nIt can take up to five business days to know whether the payment was authorized by the bank. If the payment is successful, it will appear in the Settlement details report. If it fails, you may receive a CHARGEBACK.Recurring payments\nPre-Authorized Debit Canada supports tokenization of the shopper's payment details for recurring transactions. Due to the risk of chargebacks, we do not recommend using PADs for one-off payments.\n\nYou are required to obtain a mandate from the shopper if you intend to make future recurring payments.\n\nTo make recurring payments, refer to Tokenization to:\n\nEnable the Recurring tokens life cycle events webhook.\nCreate a token through the initial payment (see Add additional parameters above).\nPay with the token in subsequent payments. Note that you do not need to include the mandate ID in the recurring payment request.\nManage tokens.\nTest and go live\nYou can test Pre-Authorized Debit Canada payments as well as chargebacks.\nTest the payment flow\nTest your integration by making test payments using the bankAccountNumber, bankLocationId, bankCode and ownerName of a real Canadian bank account. That account will not be debited.\nYou can also use the following test credentials:\n\nAccount holder name: TEST\nAccount number: 00257596\nInstitution number: 002\nTransit number: 57596\n\nTest the chargeback flow\nYou can test the return flow by making test payments with an ownerName value that consists of chargeback: followed by a PAD return reason code. For example, chargeback:05. The other account details to use are the same as when testing payments.\nNote that in the test environment the return flow goes directly to the Chargeback stage.\nReturn reason codes\nUse the following table with the most common PAD return reason codes to determine what the code means and if it is allowed to retry a returned payment.\n\n \n\n\n\nReason code\nReason\nDescription \/ Resolution\nRetry?\n\n\n\n\n01\nNSF (Debit Only)\nNon-sufficient funds (NSF). You can retry the transaction once within 30 days of the original authorization date.\n max 1x\n\n\n02\nAccount not found\nThe provided account information is incorrect. Retrying the transaction is not allowed.\n\n\n\n03\nPayment Stopped\/Recalled\nThe customer instructed their bank to not honor a payment they previously authorized. Resolve the issue with the customer. When initiating a new transaction, get a new PAD agreement from the customer. If you are going to debit the same account, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n05\nAccount Closed\nThe customer's bank account has been closed. Retrying the transaction is not allowed.\n\n\n\n07\nNo Debit Allowed\nThe provided bank account cannot be used for EFT PADs. Ask the customer for permission to charge a different, EFT PAD-enabled bank account.\n\n\n\n08\nFunds Not Cleared (Debit Only)\nInsufficient funds. You can retry the transaction once within 30 days of the original authorization date.\n max 1x\n\n\n09\nCurrency\/Account Mismatch\nThe transaction currency does not match the currency of the bank account. Retrying the transaction is not allowed.\n\n\n\n10\nPayor\/Payee Deceased\nContact the bank of the deceased account holder or account beneficiary.\n\n\n\n11\nAccount Frozen\nContact your customer to obtain a different form of payment. The bank account cannot be used while it is frozen. This return code should be a red flag for your business. If you see this code, do your due diligence around verifying the identity of your customer.\n\n\n\n12\nInvalid\/Incorrect Account No.\nThe provided account number is incorrect. Retrying the transaction is not allowed.\n\n\n\n14\nIncorrect Payor\/Payee Name\nThe provided name of the account holder or beneficiary is incorrect. Retrying the transaction is not allowed.\n\n\n\n15\nNo Agreement Existed\nThe customer informed their bank they did not give authorization for the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n16\nNot According to Agreement - Personal\nThe customer informed their bank that the payment is not in accordance with their personal PAD agreement. Suspend any recurring transactions and resolve the issue with the customer.\n\n\n\n17\nAgreement Revoked - Personal\nThe customer informed their bank they revoked their personal PAD agreement for the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n18\nNo Confirmation\/Pre-Notification - Personal\nThe consumer you tried to charge informed their bank they did not receive a confirmation or notification about the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n19\nNot According to Agreement - Business\nThe customer informed their bank that the payment is not in accordance with their business PAD agreement. Suspend any recurring transactions and resolve the issue with the customer.\n\n\n\n20\nAgreement Revoked - Business\nThe customer informed their bank they revoked their business PAD agreement for the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n21\nNo Confirmation\/Pre-Notification - Business\nThe company you tried to charge informed their bank they did not receive a confirmation or notification about the transaction. Suspend any recurring transactions and resolve the issue with the customer. If you are going to debit the same account for a new transaction, make sure the customer's bank stops blocking transactions from your company to this account.\n\n\n\n82\nInterbank Reject - Invalid Institution Number\nThe bank's institution number and\/or branch transit number is invalid, or the bank does not accept PADs.\n\n\n\n90\nInstitution in Default\nThe customer's bank has failed to fulfill its obligations. Retrying the transaction is not allowed.\n\n\n\n\n\n\n\nGo live\nBefore going live, contact our Support Team to add PADs Canada in your live Customer Area.","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Pre-Authorized Debit Canada","lvl3":"Pre-Authorized Debit Canada Web Component"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/pad","lvl3":"\/pt\/payment-methods\/pad\/web-component"},"levels":4,"category":"Payment method","category_color":"green","tags":["Advanced flow","Component"]}],"articleFiles":{"payments-response.json":"payments-response.json<\/p>"}}