- Posts: 3
- Thank you received: 0
Secure Pay
- mediaengine
- Topic Author
- Offline
- New Member
Less
More
5 years 2 weeks ago #123165
by mediaengine
Secure Pay was created by mediaengine
Hi,
We have been using the SecurePay with the Events Booking Plugin, great system. But we have a question about the transaction reference, it is pulling through the ID of the booking ID. Can we change this to the Invoice ID to allow for better cross referencing?
We also found the the Secure Pay is using a deprecated term 'Split' and could not progress passed the transaction. We changed the code to explode and now works fine. Just thought we would bring that to your attention.
Regards,
Nathan
We have been using the SecurePay with the Events Booking Plugin, great system. But we have a question about the transaction reference, it is pulling through the ID of the booking ID. Can we change this to the Invoice ID to allow for better cross referencing?
We also found the the Secure Pay is using a deprecated term 'Split' and could not progress passed the transaction. We changed the code to explode and now works fine. Just thought we would bring that to your attention.
Regards,
Nathan
Please Log in or Create an account to join the conversation.
- Tuan Pham Ngoc
- Offline
- Administrator
5 years 2 weeks ago #123166
by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Secure Pay
Hello
1. You cannot change it to Invoice ID. The reason is because in Events Booking, we only generate invoice for the registration after payment completed. The data is passed to SecurePay before payment, so we don't have that data available. So for now, you will still have to use ID for cross reference
2. Thanks for mentioning about split and explode. You can keep using the change, we changed it in the payment plugin package as well. Maybe I forgot to update it to server, will do that now
Regards,
Tuan
1. You cannot change it to Invoice ID. The reason is because in Events Booking, we only generate invoice for the registration after payment completed. The data is passed to SecurePay before payment, so we don't have that data available. So for now, you will still have to use ID for cross reference
2. Thanks for mentioning about split and explode. You can keep using the change, we changed it in the payment plugin package as well. Maybe I forgot to update it to server, will do that now
Regards,
Tuan
Please Log in or Create an account to join the conversation.
- mediaengine
- Topic Author
- Offline
- New Member
Less
More
- Posts: 3
- Thank you received: 0
5 years 2 weeks ago #123202
by mediaengine
Replied by mediaengine on topic Secure Pay
Hi Tuan,
Thankyou for your reply. To my first question is there any way we can put a prefix into transaction description? so instead of just being the id number of '29', it could be 'lesiure 29' or something similar? Our Client needs to be able to track the payments a tad easier than just an ID number.
Regards,
Nathan
Thankyou for your reply. To my first question is there any way we can put a prefix into transaction description? so instead of just being the id number of '29', it could be 'lesiure 29' or something similar? Our Client needs to be able to track the payments a tad easier than just an ID number.
Regards,
Nathan
Please Log in or Create an account to join the conversation.
- Tuan Pham Ngoc
- Offline
- Administrator
5 years 2 weeks ago #123205
by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Secure Pay
Hi Nathan
You would have to edit code if you want to change that behavior.
1. Open the file components/com_eventbooking/payments/os_securepay.php
2. Find this line of code
3. Change it to:
After that, it should work as expected
Regards,
Tuan
You would have to edit code if you want to change that behavior.
1. Open the file components/com_eventbooking/payments/os_securepay.php
2. Find this line of code
Code:
$ret = $xmlApi->processCreditStandard($data['amount'], $row->id, $data['x_card_num'], $data['exp_month'], $data['exp_year']);
3. Change it to:
Code:
$ret = $xmlApi->processCreditStandard($data['amount'], 'The prefix you want '.$row->id, $data['x_card_num'], $data['exp_month'], $data['exp_year']);
After that, it should work as expected
Regards,
Tuan
Please Log in or Create an account to join the conversation.
- mediaengine
- Topic Author
- Offline
- New Member
Less
More
- Posts: 3
- Thank you received: 0
5 years 1 week ago #123433
by mediaengine
Replied by mediaengine on topic Secure Pay
Hi Tuan,
Thankyou for your reply, this has worked perfectly!!
I have another question, we are doing our testing and have found that no Payor/Payee information is being brought through to the statements. How can we get information into that area please?
Regards,
Nathan
Thankyou for your reply, this has worked perfectly!!
I have another question, we are doing our testing and have found that no Payor/Payee information is being brought through to the statements. How can we get information into that area please?
Regards,
Nathan
Please Log in or Create an account to join the conversation.
- Tuan Pham Ngoc
- Offline
- Administrator
5 years 1 week ago #123435
by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Secure Pay
Hi Nathan
Unfortunately, the library which you are using does not have a way to pass Payer information to SecurePay, so it's not possible to do that
I will see if there is a way to handle it in the future, but right now, it's not possible
Tuan
Unfortunately, the library which you are using does not have a way to pass Payer information to SecurePay, so it's not possible to do that
I will see if there is a way to handle it in the future, but right now, it's not possible
Tuan
Please Log in or Create an account to join the conversation.
Moderators: Tuan Pham Ngoc
Support
Documentation
Information
Copyright © 2024 Joomla Extensions by Joomdonation. All Rights Reserved.
joomdonation.com is not affiliated with or endorsed by the Joomla! Project or Open Source Matters.
The Joomla! name and logo is used under a limited license granted by Open Source Matters the trademark holder in the United States and other countries.
The Joomla! name and logo is used under a limited license granted by Open Source Matters the trademark holder in the United States and other countries.