<\/code-sample>\n<\/div>\nTest and go live<\/h2>\n
Bancontact mobile does not have a test platform.<\/p>\n
We recommend that you do a penny test in the live environment, where you make a payment with a value of EUR .01<\/strong>.<\/p>","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/bancontact\/bancontact-mobile\/web-drop-in","articleFields":{"description":"Add Bancontact mobile to an existing Drop-in integration.","parameters":{"integration":"Drop-in","platform":"Web","integration_guide_url":"build-your-integration\/sessions-flow?platform=Web&integration=Drop-in","component_name":"Drop-in","component_name_capitalized":"Drop-in","payment_method":"Bancontact mobile","payment_method_type":"bcmc_mobile","component_js_const":"bcmcMobile"}},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/bancontact\/bancontact-mobile\/web-drop-in","title":"Bancontact mobile Drop-in integration","content":"This page explains how to add Bancontact mobile to your existing Web Drop-in integration.\nOur Web Drop-in renders Bancontact mobile in your payment form, and redirects the shopper to the Bancontact mobile app depending on how they are accessing your site:\n\nFor shoppers on desktop or laptop, the shopper is presented a QR code.\nFor shoppers on mobile, the shopper is switched to the Bancontact mobile app. If this fails, the shopper is presented a QR code as a fallback.\nFor shoppers on tablet, the shopper is presented with both a QR code and a button to switch to the Bancontact mobile app.\n\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built your Web Drop-in integration. \n\n\nSetup steps\nBefore you begin: Add Bancontact mobile in your test Customer Area. To receive the bcmcmobile.urlIntent parameter in the payment response: In your Customer Area, go to Developers > Additional data. Under 3D Secure select the checkbox for 3DS2 Additional Fields. \n\n\n\nAPI reference\nYou do not need to send additional fields for Bancontact mobile. To see optional fields that you can send for all payment methods, choose the endpoint you integrated:\n\n \/sessions: This is the default with Drop-in v5.0.0 or later.\n \/payments: If you implemented an additional use case.\n\nDrop-in configuration\nThere are no configuration steps specific to Bancontact mobile required for Drop-in.\nRecurring\nBancontact supports tokenization for recurring payments.\n\nWe strongly recommend that you ask explicit permission from the shopper if you intend to make future recurring payments.\n\nYou can use recurring transactions through the Bancontact Wallet Initiated Program (WIP).\nBancontact Wallet Initiated Program\nThe Bancontact Wallet Initiated Program (WIP) is a service that streamlines checkout and supports subscription-based billing. It offers the following:\n\nBancontact One-Click Pay to speed up checkout and boost conversion rates\nBancontact Recurring to support merchant-initiated recurring or subscription payments\n\nYou have to sign up to be able to use this service and not all companies are eligible to use Bancontact WIP. To enable Bancontact WIP, contact our Support Team.\nWhen you enable Bancontact WIP, transaction amount limits apply to ensure controlled and secure payments.\nShoppers go through Strong Customer Authentication (SCA) one time when they complete their first transaction and give their consent. Subsequent transactions do not require SCA, which reduces friction and improves the checkout flow. Because the first transaction goes through SCA, there is no liability shift. The issuer remains liable.\nMake a recurring payment\nTo make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nTo test recurring payments, contact our Support Team to configure your test environment.\nCreate a token\nTo create a token, include in your \/sessions or \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper (minimum length three characters).\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: The pspReference of the initial payment.\nstoredPaymentMethodId: This is the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook. You can also get this value by using the \/listRecurringDetails endpoint.\nshopperReference: The unique shopper identifier that you specified when creating the token.\nshopperInteraction:\u00a0ContAuth.\nrecurringProcessingModel: Subscription or UnscheduledCardOnFile.\n\nFor more information about the shopperInteraction and recurringProcessingModel fields, refer to Tokenization.\nThe following example shows a recurring Subscription payment using WIP.\n\n \n\nTest and go live\nBancontact mobile does not have a test platform.\nWe recommend that you do a penny test in the live environment, where you make a payment with a value of EUR .01.","type":"page","locale":"pt","boost":16,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Bancontact","lvl3":"Bancontact mobile","lvl4":"Bancontact mobile Drop-in integration"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/bancontact","lvl3":"https:\/\/docs.adyen.com\/pt\/payment-methods\/bancontact\/bancontact-mobile","lvl4":"\/pt\/payment-methods\/bancontact\/bancontact-mobile\/web-drop-in"},"levels":5,"category":"Payment method","category_color":"green","tags":["Bancontact","mobile","Drop-in","integration"]}}