Skip navigation
_zoe
Currently Being Moderated

NAB Transact IDs

Apr 11, 2012 12:06 AM

Tags: #payment_gateway #nab

Hi People at BC

 

We've just been sent our NAB Transact IDs for both Direct Post and API. When using our Merchant IDs in the 'username' field, we receive the following error:

 

ERROR: An error occurred while processing credit card
Invalid merchant ID 504.

 

The Merchant ID we have has two letters and five numbers, but the Knowledgebase suggests that a Merchant ID for NAB Transact should have three letters and four numbers (http://kb.worldsecuresystems.com/833/cpsid_83342.html?bc-partner). 

I also noticed that on another forum post (http://www.businesscatalyst.com/ForumRetrieve.aspx?A=New&ForumID=1737& TopicID=20503&ParentID=0&NoTemplate=False#catforumeditor) it is recommeded that we use our Client ID, not our Merchant ID.

 

Would you mind providing some clarity around this?

 

Thanks

 
Replies
  • Currently Being Moderated
    Apr 11, 2012 12:31 AM   in reply to _zoe

    From memory, I am quite positive that the username/merchant ID must be a 7 digit number and cannot be anything else. If your Client ID happens to be a 7 digit number, I suggest trying that.

     

    I also suggest using the live NAB gateway and not the test gateway, and instead testing with a $1 product if you aren't already.

     
    |
    Mark as:
  • Liam Dilley
    6,716 posts
    Feb 28, 2012
    Currently Being Moderated
    Apr 11, 2012 1:09 AM   in reply to _zoe

    It is not a 7 digit number, it is a number and letters - 3  letters + 4 numbers. Based on what your saying Zoe I would stab at looking at if one of the numbers is actually a letter. So if it is 0- try o instead.

     
    |
    Mark as:
  • Liam Dilley
    6,716 posts
    Feb 28, 2012
    Currently Being Moderated
    Apr 11, 2012 7:42 PM   in reply to _zoe

    I do not use it and you will need to contact NAB I think. There should be 3 characters. IF they have made any changes to their system where that is not the case and not made that change clear to developers (Such as BC) and new accounts do not work in BC then BC will need to update their system to support that.

    It could be that or it is  the wrong number etc. I would give NAB support a go, Quote the knowledgebase link for setup with BC and see what they come back to you with.

     

    I never set it up with this company, just basing my thoughts on common issues people run into etc.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 15, 2012 7:35 PM   in reply to _zoe

    FYI... when one of my clients was originally supplied their credentials by the NAB (in email format) it was not actually the correct details we required. I ended up having to call and be told something different by the call center staff. So yes, calling to confirm what the details are would be a good idea !

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 29, 2012 9:43 PM   in reply to _zoe

    Something else to make sure of (especially if you havent done this before)..... when your client helpfully says "yes I have changed the password from the default one ... its now xxxyyy etc" ... be sure they have manually gone in and changed their API Transaction password from the default abcd1234... which is a separate issue from changing the login password. Some clients may be unaware of this.

    nab password.jpg

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 14, 2012 9:02 PM   in reply to Liam Dilley

    It should be 2 characters FYI.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points