Bendigo Payment Gateway (MPGS) - Magento 2

Bendigo Bank Payment Gateway (MPGS) - Magento 2 allows to process credit card payments online directly transferred into your bank account through Bendigo Payment Gateway 

After customers choose payment method on website, it will be redirected to payment gateway and make payment. After paying successfully on payment gateway, it will redirect to shop’s website and then update status for the order. 

If your merchant account is using Bendigo Bank MiGS Merchant's Portal. We recommend: Bendigo Bank Payment Gateway (MiGS) - Magento 2

Payment Options

Bendigo Direct Payment: Allow your customer to purchase directly from your site using Credit Cards.

Bendigo Hosted Checkout: Redirect to the Gateway website for credit card entry, then redirect back to your confirmation page once successful.

Requirements

In order to use the extension, you must have a merchant account and login credentials to Bendigo MPGS Merchant's portal provided by Bendigo Bank.

Features of Bendigo Bank Payment Gateway - Magento 2

• 3D-Secure V2 (3DS2), EMV 3D Secure (apply to Hosted Checkout)
• Support Credit/Debit Cards
• Secure Checkout Process
• Encrypted the payment credentials
• Capture New Sales 
• Authorize and Capture
• Refund Online
• Create invoice automatically.
• Support SSL Certificate
• Support multiple websites
• Support multiple store views
• Support multiple currencies
• Unlimited domains

3D-Secure V2 (3DS2) Authentication Flows

1. A payer browses your shop site, selects one or more products, proceeds to the payment page, and selects to pay with a card that supports 3DS1 and 3DS2.

2. Initiate Authentication: You ask the gateway to check with the card scheme if the card is enrolled for 3DS.

3. If 3DS authentication of the payer is available, the gateway returns the authentication details in the response.

4. The gateway returns details of the supported ACS call. You must submit the ACS call details as a form post in a hidden iframe, so that the ACS can collect additional data.

5. Authenticate Payer: You ask the gateway to perform the initiated authentication.

6. The gateway provides you with details of the authentication for a challenge flow (where the payer is required to respond to a challenge presented by the issuer). If the issuer requires the payer to respond to a challenge, you redirect the payer’s web browser to the ACS, which presents its authentication UI. The issuer returns the authentication result to the gateway. The gateway redirects the payer directly to your website.

7. Use the 3DS Authentication Transaction ID in a Payment Operation: You submit the payment for processing.

8. You display the order confirmation page to the payer.

Test Environment

Why Choose Our Extension