|
Waz
|
July 11, 2016 at 12:27 am
HI Guys
I am still on EE3 and Using NAB gateway but unfortunately my NAB gateway has just failed and it appears that it is perhaps due to changes in NAB requirements to the fingerprint field with the addition of the EPS_TXNTYPE field.
2.3.2. Transaction Type – EPS_TXNTYPE
CLASS Mandatory
FORMAT Numeric
DESCRIPTION Used to determine the processing type for an individual transaction and is included within the fingerprint.
This is used to switch between payments, preauthorisations and the added features of Risk Management
and 3D Secure. Payments and preauthorisations are described in the following sections.
Other transaction types are listed in Appendix 2: Transaction Types.
2.3.2.1. Payment
Payments are real-time, immediately authorised card transactions. Transaction information is passed from a payment form to your
NAB Transact account for immediate processing. The transaction type for payments is equal to 0.
TYPICAL USE <input type=”hidden” name=”EPS_TXNTYPE” value=”0″>
pre-info
(i’ve updated the NAB url to v2)
https://transact.nab.com.au/live/directpostv2/authorise
The Direct Post v2.1.2 – Integration Guide states
To generate a fingerprint, your system will need to create a SHA1 hash of the following mandatory request
fields:
EPS_MERCHANT|TransactionPassword|EPS_TXNTYPE|EPS_REFERENCEID|EPS_AMOUNT|EPS_TIMESTAMP
Where the EPS_ prefixed fields are sent in the request and the Transaction Password is obtained from NAB
Transact, which may be changed via the NAB Transact Management Portal
Example: Setting the fingerprint
Fields joined with a | separator:
XYZ0010|abcd1234|0|Test Reference|1.00|20140224221931
SHA1 the above string: 7be3248e35ad189193d8ecd4273ad3b9fd069e90
<input type=”hidden” name=”EPS_FINGERPRINT” value=”7be3248e35ad189193d8ecd4273ad3b9fd069e90″>
TYPICAL USE <input type=”
From this (I am just a novice with coding) I asusme that a new EPS_FINGERPRINT variable needs to be constructed with the addition of EPS_TXNTYPE and then converted to a SHA1 hash.
Any chance you would be able to help here with what I need to change the script to?
Thanks in advance
|
|
Tony
|
July 11, 2016 at 10:23 am
Hi there,
I am still on EE3 and Using NAB gateway but unfortunately my NAB gateway has just failed and it appears that it is perhaps due to changes in NAB requirements to the fingerprint field with the addition of the EPS_TXNTYPE field.
Did the payment gateway fail before you changed NAB url to v2?
The gateway uses v1 of the API which generates the EPS_FINGERPRINT through nabs servers via a separate request. V2 of allows you to do do this on your own server (without the need of an additional request) using the EPS_TXNTYPE field so v1 should continue without a problem.
Can you link me to an event I can use to view the problem?
|
|
Waz
|
July 11, 2016 at 3:34 pm
Hi Tony
Thanks for your assistance. Yes the gateway failed (last Tuesday) out of no where before any edits were made. I kept getting continually “invalid fingerprint” errors. I am not sure if NAB have now stopped v1 from being able to be used? Can you send me an email direct and I can give you details on the test site so you can see this error? I’d prefer not to post details here thanks
|
|
Tony
|
July 12, 2016 at 2:43 am
You can send the link to support[at]eventespresso.com
If we need login details to view the site I’d recommend you use this form:
https://eventespresso.com/send-login-details/
|
|
Waz
|
July 12, 2016 at 3:43 am
Thanks Tony, I have just sent you details of a test site and login via the form, cheers
|
|
Tony
|
July 12, 2016 at 4:14 am
Using FTP can you place this version of the NAB gateway within /wp-content/uploads/espresso/gateways/
http://take.ms/RIz03
So you should end up with /wp-content/uploads/espresso/gateways/nab/ which contains all of the nab gateway files.
Also I would recommend updating to the latest version of EE3, although I don’t think its related to your current issue.
|
|
Waz
|
July 12, 2016 at 4:37 am
Hi Tony
Thanks for you help again. The files were uploaded to the test site. Did you just changed the response value in nab.php?
I am not sure if this is just a diagnostic test, but the change has now allowed the payment to be processed (cc charged successfully) but EE appears to not be notified (attendee payment status is unpaid) – see my live transaction and the final URL is
https://transact.nab.com.au/live/directpost/authorise
cheers
|
|
Tony
|
July 12, 2016 at 5:08 am
Yes the only change made to the gateway was the value used from the response, your site had no fingerprint set at all which would then show invalid fingerprint, simply because there wasn’t one.
I am not sure if this is just a diagnostic test, but the change has now allowed the payment to be processed (cc charged successfully) but EE appears to not be notified (attendee payment status is unpaid) – see my live transaction and the final URL is
https://transact.nab.com.au/live/directpost/authorise
That’s not an issue with the change made (the fingerprint is required and must be included) I’ll need to check into this further.
|
|
Waz
|
July 13, 2016 at 6:12 am
Hi Tony
Thanks for the clarification. Were you able to work out what is going on here?
|
|
Tony
|
July 14, 2016 at 4:12 am
Hi Warren,
I ran some testing on a couple of sites and could not reproduce the same problem.
I logged back into your test site to take another look there and notice you are now using EE4, are you switching over to use EE4 on the live site?
You’ll find NAB is supported within EE4 though Mijireh.
|
|
Waz
|
July 14, 2016 at 10:15 pm
Hi Tony
Thanks for looking at this for me and confirming this for me. I also believe the error is not on my side of things. Anyway, as a result of all of this, yes I have been looking at other options including EE4 to circumvent such issues.
|
