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
Custom Payment Gateway - file examples? | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › Custom Payment Gateway – file examples?

Custom Payment Gateway – file examples?

Posted: September 5, 2013 at 8:13 pm

Viewing 1 reply thread


Sol Ace

September 5, 2013 at 8:13 pm

Hi

I have read about the method to create a custom payment gateway and I am reasonably confident that I can manage this, however, before I commit to buy the plugin, I would like to look at the example files that are suggested in the article
http://staging.eventespresso.com/wiki/custom-gateway-integration/

In particular
– gateways/aim/aim_vars.php
– gateways/authnet/authnet_vars.php
– gateways/gateway_display.php
and the paypal standard file if possible.

Please advise if this is possible?

Thanks
Sol


Josh

September 5, 2013 at 9:44 pm

Hi Sol,

I can advise downloading the lite version of Event Espresso from wordpress.org:

http://wordpress.org/extend/plugins/event-espresso-free/

It has all of the centralized gateway files and the PayPal gateway files.

Viewing 1 reply thread

The support post ‘Custom Payment Gateway – file examples?’ 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 Josh 11 years, 4 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server