Support

Home Forums Event Espresso Premium Transaction page – how should it work

Transaction page – how should it work

Posted: April 5, 2016 at 2:07 am


Emil

April 5, 2016 at 2:07 am

Hi,

We’ve just set our first credit card payment gateway through our local credit card processing provider. They created a payment gateway module for EE4 for us, following the EE guidelines and template for the module.
We tested the implementation of this payment gateway yesterday with a dummy credit card info provided by our credit card processing company dev team. The payment process worked, but the payment was declined (we knew that would happen, because we used a dummy credit card).
I have some questions regarding the normal behaviour of Transactions Page, Thank You Page and Cancelled Registration Page.
For example, after finishing the registration after using the dummy credit card, I was redirected to the Transactions Page, which had the following content:
“This is the Event Espresso Transactions page. This page receives instant payment notification (IPN) requests and should have a status of published, but should not be easily accessible by site visitors. Do not add it to your website’s navigation menu or link to it from another page. Also, do not delete it or change its status to private.”

This content is not something we want the user to see. Does this mean that the guys who created the custom payment module for us did something wrong or they didn’t something they should do in order to connect their payment gateway with EE? Or there is something we have to do in order to show some specific content on this page?
The question is, what should a user who completed a transaction should see on the Transaction page after a credit card payment, either is a successful one, or a failed one? How can we set things properly for this to work fine?
The same question goes for the rest of the pages the visitor is redirected to after completing a credit card payment: Thank You Page and Cancelled Registration. How do we connect them properly with the payment gateway module and how can we show customized content on them?
If there’s documentation on this, please point me to it. If not, please let me know how to do the things above.
Thank you.
Best Regards,
Emil


Tony

  • Support Staff

April 5, 2016 at 5:22 am

Hi Emil,

This content is not something we want the user to see. Does this mean that the guys who created the custom payment module for us did something wrong or they didn’t something they should do in order to connect their payment gateway with EE?

I’m going to double check this with the developers (it will take a little due to time differences), but it does sound the Payment Method has not been created correctly.

You should not be directed to the Transactions page, ever. It is not used by Event Espresso to display anything useful to the user, it is to process IPN’s sent to your site from your payment processor.

Or there is something we have to do in order to show some specific content on this page?

No, see above.

The question is, what should a user who completed a transaction should see on the Transaction page after a credit card payment, either is a successful one, or a failed one?

It depends on the Payment method, but on successful payment you should be directed to the Thank you page, on a fail payment you can either display a fail message and remain on the same page for them to try again or direct them to the thank you page and show incomplete (might be a little confusing)

The same question goes for the rest of the pages the visitor is redirected to after completing a credit card payment: Thank You Page and Cancelled Registration. How do we connect them properly with the payment gateway module and how can we show customized content on them?

The thank you page is dynamically created using the details from the registration.

The canceled page is not a payment cancelled page, it is a registration cancelled page. Meaning they completely cancel the registration to start another (you don’t want this for payments)

Is the payment method on-site or offsite?

Did they use this documentation:

https://eventespresso.com/2015/03/developers-guide-to-payment-methods-for-event-espresso-4-6/

(There are various links from there depending on the Payment method)


Lorenzo Orlando Caum

  • Support Staff

April 5, 2016 at 5:24 am

Hi Emil,

The transactions page won’t be visible to a registrant/attendee during registration checkout. It helps with payment processing with in the background. One example of a payment gateway that uses an IPN would be PayPal which means the transaction is updated in the background as they arrive to the thank you page for Event Espresso.

We have documentation on writing a payment gateway here:

http://developer.eventespresso.com/docs/ee4-payment-method-development/

I recommend reaching out to our developers via Github so they can share feedback:

https://github.com/eventespresso/event-espresso-core/issues

Be sure to share some specific information about the payment gateway:

Name of payment gateway

Offsite (transaction takes place on another server and then they are returned to your site) or Onsite (e.g. a credit card is processed without a registrant/attendee leaving your site)

A copy of what you have so far


Lorenzo

The support post ‘Transaction page – how should it work’ 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.

Event Espresso