• Resolved Praxia

    (@praxia)


    Hello. I have a client’s site setup on separate staging domain and have entered all settings and credentials as provided. The payment gateway is displaying fine and appears to be setup correctly, yet when any number is entered in the credit card field number, the following error is produced: “SyntaxError: Unexpected token o in JSON at position 1”.

    So, what I need to be able to do is conduct test transactions. I’m wondering if the plugin solution being installed on a different domain than the production site has anything to do with this issue.

    Thank you.

    • This topic was modified 3 years, 4 months ago by Praxia.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author RexAK

    (@rexak)

    @praxia Sounds like a plugin or theme conflict.
    Please disable plugins one at a time and check if the issue still persists. Switch to another theme and see if this problem still exists.

    If the problem still is present, then you will need to reach out to your, or your client’s, CardPointe rep, and have them assist with troubleshooting.

    Plugin Author RexAK

    (@rexak)

    @praxia Quick question: do you haven to have the LastPass password extension enabled on your browser? I’ve seen issues with it…

    Thread Starter Praxia

    (@praxia)

    Hi RexAK,

    @rexak Uncanny how you read my mind. I just came back here to comment that I found out this issue is being caused by the Awesome Screenshot extension in Chrome, so please let the dev team know. The error is no longer occurring after deactivating that extension. Now I need to run test transactions without incurring actual billing. Can you advise on that process and where I can find documentation on it? Thank you.

    • This reply was modified 3 years, 4 months ago by Praxia.
    • This reply was modified 3 years, 4 months ago by Praxia.
    Thread Starter Praxia

    (@praxia)

    @rexak To clarify further on testing needs, I’m already set up in sandbox mode, yet I’d like to see some usage documentation on sandbox mode, or at least confirm what credit card numbers and CVC codes will validate during testing. Thank you.

    Plugin Author RexAK

    (@rexak)

    @praxia

    Glad you were able to find the issue.

    You can use 4111 1111 1111 1111 to test VISA type cards, and see this publicly available doc for testing codes and responses: https://developer.cardpointe.com/guides/cardpointe-gateway#understanding-the-uat-environment.

    Marking as resolved.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘SyntaxError: Unexpected token’ is closed to new replies.