CommBank CommWeb MPGS Payments

Commonwealth Bank (CommWeb MPGS) extension allows you to use CommWeb as a credit card processor using their fully integrated API process. You can process Visa and Mastercard by default and can optionally accept American Express, Diners Club and JCB after further activation by Commonwealth Bank.

CommWeb Payment Gateway is a payment service provided by the Commonwealth Bank of Australia that facilitates the payment process of shoppers. 

Account & Pricing

In order to use the extension, you need to have a CommWeb merchant account provided by CommBank, and they will give you the credentials to access the Merchant Portal.

To see the Pricing Plans, you need to contact CommBank Team

Payment Integration Options

The extension integrates two payment methods, which will be shown in the Magento admin panel after it's installed successfully.

CommWeb Direct Payment: Keep your customer on your site during the entire checkout process

CommWeb Hosted Checkout: Direct your customer to a secure payment form during the checkout process. Once they’ve paid, they’ll be redirected back to your site

Features of CommWeb Hosted Checkout

• Support merchants using CommWeb with MPGS merchant accounts
• Support EMV 3D Secure (3DS2)
• Support Credit/Debit Cards
• Secure Checkout Process
• Encrypted the payment credentials
• Capture New Sales 
• Authorize and Capture
• Refund Online
• Create an invoice automatically.
• Support SSL Certificate
• Support multiple websites
• Support multiple store views
• Support multiple currencies
• Unlimited domains. 

Features of CommWeb Direct Payment

• Support merchants using CommWeb with MPGS merchant accounts.
• Support Credit/Debit Cards
• Secure Checkout Process
• Encrypted the payment credentials
• Capture New Sales 
• Authorize and Capture invoice online
• Create Invoice Automatically
• Refund Online
• Support SSL Certificate
• Support multiple websites
• Support multiple store views
• Support multiple currencies
• Unlimited domains

Webhook Notifications

In case the transaction response failed to come back for this transaction. This can happen due to an interruption in the customer's browsing session. Your checkout redirects customers to CommWeb and awaits the response to come back at the end. The response comes back through the customer's browser with the redirection back to your success or error page. It majority of cases this works well. However, if your customer closes the browser rather than waiting for the redirect, or if their lose connection, or their browser does not retain the response, etc. Your checkout does not receive the response and does not update with the outcome of the transaction.

If  Webhook Notifications is used. It works by checking the transaction with the CommWeb merchant's Portal if there is no response after a certain about of time (i.e 15 minutes). If the transaction is not found by Webhook Notifications, it means the customer did not submit their payment after the redirect. But if it was submitted, your website will learn whether the transaction was approved or declined.

Test credit cards 

Mastercard: 5123450000000008 Expiry Date: 01 / 39 3-D Secure Enrolled: Y

Mastercard: 2223000000000007 Expiry Date: 01 / 39 Secure Enrolled: Y

Mastercard: 5111111111111118 Expiry Date: 01 / 39 Secure Enrolled: N

Mastercard: 2223000000000023 Expiry Date: 01 / 39 Secure Enrolled: N

Visa: 4508750015741019 Expiry Date: 01 / 39 3-D Secure Enrolled: Y

Visa: 4012000033330026 Expiry Date: 01 / 39 3-D Secure Enrolled: N

Security & PCI Compliance

Once the customers add products to their cart and proceed to pay using the CommWeb Payment Gateway, they are asked to add card details on-site, which will be transferred back to the merchant’s server before being transferred to the CommWeb server.

Since merchants do not store or process customer payment information, they will be able to handle more customers. Merchants using the CommWeb API integration will be eligible to validate PCI DSS using the SAQ A-EP level of compliance.