|
bakerrisk
|
June 19, 2019 at 1:37 pm
Hi,
We offer training courses and sometimes the registrant’s company will pay for their course fee. Our Authorize.net transaction detail does not include the registrant’s information because the payment information entered is for the company or the name on the company card.
So in order to verify a company’s payment for a registrant, we have to find the matching card number from the transaction details > billing information > card number with a registrant.
But to help streamline matching up a registrant with a company’s card payment, the accounting department is asking if we can add the card number from the transaction details to the admin’s payment received message. With this in the email message, they won’t have to log in to view the transaction details to verify the card number matches with the Authorize.net transaction summary.
We looked through the available shortcodes in the message template but did not find anything that would let us do this.
How can we grab the card number from the transaction details to put into the admin’s payment received message template?
Thanks in advance.
|
|
Tony
|
June 24, 2019 at 7:39 am
Hi there,
Just to clarify, EE only stores the last 4 digits of a card number, never the full number. I’m guessing this is something you are already aware of but others reading this may not be so just noting it here.
Along with the above EE can usually only store the above details when using an ‘on-site’ payment method (which requires the highest level of PCI compliance) as that’s the only time EE will have access to that data, in this case that may complicate things as I’m assuming you are using the Auth.net AIM payment method integration, is that correct?
The reason that may complicate this is Auth.net have deprecated that integration method in favour of their ‘Accept’ API (which we use with the EE4 Auth.net Accept Payment method), meaning the AIM payment method will eventually stop working and means you’ll need to switch to another whenever they decide to EOL the AIM api.
Right now don’t have any shortcodes to pull the information you are requesting in the messages system and whilst you could add your own custom shortcodes used to pull whatever data you need, you would be doing so with an integration that will (eventually) be closed down. The Accept API integration we have is not an ‘on-site’ payment method and so will not store the card numbers in the transaction either, meaning you will basically be adding custom shortcodes specifically for this add-on.
Rather than the above, would the Txn ID from Auth.net work for you?
For example – https://monosnap.com/file/XPaOyjq9oIUEtbqociC2gF3Zb8N37V
|
|
bakerrisk
|
June 24, 2019 at 8:58 am
Thanks for the explanation about Auth.net AIM, we are using the Auth.net AIM payment method right now and thanks for letting us know about the possibility they may discontinue the AIM API. We understand any custom shortcodes related to the AIM API can become useless when they decide to EOL it.
We like your suggestion about using the Txn ID from Auth.net. Will the ability to grab that data change when we have to switch to the Accept API?
We would like to move forward with the Txn ID from Auth.net to match up payments with registrants.
Could you help with us with how we can grab and add the Auth.net Txn ID to the email message?
Thanks.
|
|
Tony
|
June 24, 2019 at 10:54 am
We like your suggestion about using the Txn ID from Auth.net. Will the ability to grab that data change when we have to switch to the Accept API?
It shouldn’t do no, the payment provided TXN ID is saved to the EE_Payment object and isn’t really a payment provider specific feature, even then pretty much every payment provider will have a transaction ID for the payment you’ve just created so it shouldn’t change (I know that our Auth.net Accept payment method saves the value).
Could you help with us with how we can grab and add the Auth.net Txn ID to the email message?
You’ll need a custom shortcode for the messages system, we have some details on how to create one here:
https://eventespresso.com/wiki/messages-system-how-to-add-custom-message-shortcodes/
The library you need to add a shortcode/parser to in this case is likely EE_Transaction_Shortcodes and I would recommend you view the \event-espresso-core-reg\core\libraries\shortcodes\EE_Transaction_Shortcodes.lib.php file to see how the parse ensures it has an EE_Payment object.
|
