error in hosted tokenization " https://esqa.moneris.com SENT - 942-undefined-invalid credentials"

Hi,

when i hit on submit iframe button immediately i get an error message " https://esqa.moneris.com SENT - 942-undefined-invalid credentials" although i have entered valid profile id.

could you please look into this and thanks in advance.

  • RR_Moneris

    In reply to pink:

    Thanks for the feed back... it sounds like the concern is just about un escaped ampersands. I will raise it with our documentation team.
  • RR_Moneris

    In reply to pink:

    Thanks for the feed back... it sounds like the concern is just about un escaped ampersands. I will raise it with our documentation team.
  • Maple2017
    Hi,
    I'm having the same error, no matter what I do...
    I've tried out profiles generated for monca02086, but none of them works.
    I think correct one should be htGP28U596DVXN8?
    URI:
    https:///esqa.moneris.com//HPPtoken//index.php?id=htGP28U596DVXN8&css_body=background:white;&css_textbox=borderwidth:2px;&css_textbox_pan=width:140px;&enable_exp=1&css_textbox_exp=width:40px;&enable_cvd=1&css_textbox_cvd=width:40px&css_label_pan=1
    I tried cards 4242424254545454 and 4111111111111111.
    Please advise what I have done wrong.
  • RR_Moneris

    In reply to Maple2017:

    What are you getting for an error? It could be related to the source URL not matching with what you have configured. Instead of having the whole URL just have the domain. You can also bypass the source to test if that's your issue. In production keep in mind you will want to have signed cert even if your are not collecting the card data.
  • Maple2017

    In reply to RR_Moneris:

    RR_Moneris, thank you for response.
    I use test, and I get the error below when I press "submit to Moneris":

    This is the outer page
    https://esqa.moneris.com SENT - 942-undefined-invalid credentials

    I have already replaced profile Id in frame source with my profile.
    I tried profile Id generated for http://***demo.centralus.cloudapp.azure.com - is that what you've supposed?
    Still no success...
  • RR_Moneris

    In reply to Maple2017:

    Can you try a profile with no source domain and let me know?
  • Maple2017

    In reply to RR_Moneris:

    I figured out - it seems the reason was that it was called from http://***demo.centralus.cloudapp.azure.com:12018, with port number despite the profile was created without it. Once I reconfigured everything without port number, I was able to get temporary token.
    Thank you!
  • RR_Moneris

    In reply to Maple2017:

    Ok, thanks for letting us know.