Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
CommWeb (Commonwealth Bank of Australia) Payment Gateway | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › CommWeb (Commonwealth Bank of Australia) Payment Gateway

CommWeb (Commonwealth Bank of Australia) Payment Gateway

Posted: July 11, 2013 at 6:57 pm

Viewing 1 reply thread


abrowning

July 11, 2013 at 6:57 pm

I understand that ANZ eGate and CommWeb (Commonwealth Bank of Australia) use the same MIGS payments platform from Mastercard. Since you already have the ANZ eGate gateway written, would it be very expensive to get a CommWeb version put together.


Dean

  • Support Staff

    •

July 12, 2013 at 4:33 am

Hi,

I cannot give you a costing, but if you fill out the custom gateway form, one of the developers/sales team can respond in more detail to you.

http://staging.eventespresso.com/rich-features/multiple-pricing-options/custom-payment-gateway-development/
Viewing 1 reply thread

The support post ‘CommWeb (Commonwealth Bank of Australia) Payment Gateway’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Status: closed

Updated by Dean 11 years, 6 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server