Kirill Gromov

Mercado Pago Gateway Accept payments through Mercado Pago Checkout Pro directly from your Invision Community 5 Commerce checkout. Customers complete their purchase on Mercado Pago’s hosted payment page, then return to your community while the gateway updates their transaction status. The integration verifies signed webhooks and confirms payment details with Mercado Pago before approving a Commerce transaction. It supports pending and rejected payments, retries after a failed payment attempt, full and partial refunds, and chargeback alerts. Administrators can configure installments, payment-type exclusions, binary mode, and a statement descriptor. Requirements: Invision Community 5 with Commerce, a Mercado Pago account with an Access Token and webhook secret, and a publicly accessible HTTPS site. Recurring payments are not supported. File Information Submitter Kirill Gromov Submitted 09/13/26 Category Paid apps for Invision Community 5 View File

Binance Pay Gateway Accept Binance Pay payments in Invision Community 5 Commerce. Customers complete payment on Binance Pay’s hosted checkout page, while the gateway tracks the order and updates their Commerce transaction when payment is confirmed. FeaturesCrypto-denominated or fiat-denominated orders Signed API requests and verified webhook notifications Automatic handling of successful, pending, canceled, and expired payments Full refunds through Commerce, with confirmation from Binance Pay Protection against duplicate payment notifications Requirements: Invision Community 5 with Commerce, a Binance Pay merchant account, API credentials, and a public HTTPS webhook URL. Please note: Recurring payments and partial refunds are not supported. File Information Submitter Kirill Gromov Submitted 09/13/26 Category Paid apps for Invision Community 5 View File

GoCardless Gateway Accept one-time bank payments in Invision Community Commerce with a GoCardless-hosted payment flow. Customers authorise their payment on GoCardless and return to your community, while Commerce keeps the transaction pending until GoCardless confirms collection. Configure a gateway for a supported Pay by Bank or Direct Debit scheme and its currency. The integration verifies signed webhooks, handles payment failures and duplicate notifications, and supports full or partial refunds when the payment is eligible through GoCardless. Requirements: Invision Community 5 with Commerce, a GoCardless account, an API access token, and an HTTPS webhook endpoint. Note: Automatic recurring billing agreements are not supported. File Information Submitter Kirill Gromov Submitted 09/13/26 Category Paid apps for Invision Community 5 View File

dLocal Gateway Accept one-time payments in Invision Community 5 Commerce through dLocal’s hosted checkout. Customers complete payment on dLocal’s secure page, where they can choose from available payment methods or use a method you configure in advance. Key featuresHosted checkout keeps card entry off your community. Sandbox and Production modes with separate credentials. Signed payment notifications and server-side status verification, including delayed payments. Full and partial refunds, including asynchronous refund updates, where supported by dLocal. Chargeback notifications that flag disputed transactions and alert administrators. Requirements: Invision Community 5 with Commerce, a dLocal merchant account, and publicly accessible HTTPS callback URLs. Available payment methods depend on your dLocal account and the customer’s country. Recurring payments and subscriptions are not supported. File Information Submitter Kirill Gromov Submitted 09/13/26 Category Paid apps for Invision Community 5 View File

Razorpay Gateway Accept payments through Razorpay directly from Invision Community 5 Commerce. Customers select Razorpay at checkout and complete their payment in a popup on your site. Available payment methods, such as cards, UPI, netbanking and wallets, depend on your Razorpay account. The integration creates a Razorpay order for each transaction, verifies payment signatures and server notifications, and confirms the payment before Commerce fulfills the purchase. It supports full and partial refunds from the Commerce AdminCP, payment retries, and background reconciliation when a notification is delayed. Requirements: Invision Community 5 with Commerce, a Razorpay account, API keys, and a public HTTPS webhook URL. Automatic recurring charges and stored cards are not supported. Refunds made directly in the Razorpay Dashboard require manual reconciliation in Commerce. File Information Submitter Kirill Gromov Submitted 09/13/26 Category Paid apps for Invision Community 5 View File

Cybersource Gateway Accept one-time payments through Cybersource Secure Acceptance Hosted Checkout. Customers enter their payment details on a Cybersource-hosted page, while your Invision Community 5 Commerce store receives signed payment responses and updates the order. Features One-time sales and authorization-then-capture payments Signed customer returns and Merchant POST notifications Handling for accepted, declined, cancelled, review, and error responses Authorization reversals and voids for eligible sales or captures Full refunds and partial refunds that leave a remaining balance Sandbox and production settings, with protection against duplicate processing Requirements and limitations Requires Invision Community 5 Commerce, a Cybersource Secure Acceptance profile, REST API credentials, and publicly reachable HTTPS callback URLs. Recurring billing and stored cards are not supported. Test the complete payment flow in your Cybersource sandbox before enabling production payments. File Information Submitter Kirill Gromov Submitted 09/13/26 Category Paid apps for Invision Community 5 View File

Adyen Gateway Give customers a secure, familiar checkout experience while keeping payment processing with Adyen. The gateway creates a Hosted Checkout session, redirects the customer to Adyen, and updates the Commerce transaction using HMAC-verified webhooks. FeaturesSupports payment methods enabled for your Adyen merchant account, including cards, 3D Secure, wallets, and redirect methods. Handles successful, pending, refused, canceled, and expired payments. Supports full and partial refunds, including asynchronous refund outcomes. Detects duplicate notifications and supports payment retries. Routes capture failures and chargebacks to an administrator attention workflow. Includes separate test and live settings, plus HMAC key rotation. Requirements: Invision Community 5 with Commerce, an Adyen merchant account, and a publicly accessible HTTPS webhook URL. Available payment methods depend on your Adyen account and configuration. Scope: One-time payments only. Recurring billing, manual capture, marketplace splits, and Adyen partial-payment Orders are not included. File Information Submitter Kirill Gromov Submitted 09/13/26 Category Paid apps for Invision Community 5 View File

Square allowed a one-time authorization, but rejected a separate verification when saving a card for auto-renewal. When POSTing /v2/cards, Square performs a verification request for $0; if it fails, INVALID_CARD_DATA is returned. The plugin then cancels authorization to avoid charging for a subscription that cannot be renewed. These logs don't reveal why the $0 verification failed. It's possible the bank refused to save the card for future debits, there was a mismatch in the verification data, or there was a problem with the Square Application ID and Access Token. CVV_ACCEPTED refers to the first authorization and doesn't mean saving the card was approved. Version 2.1.2 provides Square with a more complete address and name, but I can't honestly say the lack of this data is a confirmed cause or promise that the update will fix the failure. Square can verify the exact cause for this card using the failed request ID /v2/cards.