Google Pay live issue

  • Resolved meroving

    (@meroving)


    2 weeks, 5 days ago

    Hello, I could successfully integrate the Google Pay on sandbox and we got the Google Approve status. However, on the live we got OR_BIBED_11 error code. I made a short investigation and it looks like that the Merchant ID is not sent by the plugin. If I add this in the console and then click on the Pay the Google Payment looks ok.
    In the “Authorize.Net Google Pay – By Easy Payment” gateway I did not find the way to add our Merhcant ID. Could you please help me where we need to add it?

    The log shows ok:

    2026-05-07T01:02:01+00:00 Info EASYAUTHNET_AuthorizeNet_API_Handler::fetch_merchant_details: Successfully retrieved client key | {“client_key”:”8v***8s”}
    2026-05-07T02:06:57+00:00 Info EASYAUTHNET_AuthorizeNet_API_Handler::fetch_merchant_details: Fetching merchant details for client key | {“environment”:”live”,”api_login_id”:”9m***6t”}

    Thank you in advance!
    Regards, M

    • This topic was modified 2 weeks, 5 days ago by meroving.
    • This topic was modified 2 weeks, 5 days ago by meroving. Reason: added logs
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Jignesh

    (@jigneshmpatel)

    2 weeks, 5 days ago

    Hello,

    Thank you for providing detailed information about the issue. I am currently investigating and attempting to reproduce the problem on my end. I will update you as soon as I have more insights or a solution.

    Thank you for your patience.

    Best regards

    Plugin Support Jignesh

    (@jigneshmpatel)

    2 weeks, 5 days ago

    Hello,

    We have included a fix for the issue you reported in this version (1.0.12.1) : Download Link

    Please try this and let us know how it works for you 

    Best Regards

    Thread Starter meroving

    (@meroving)

    2 weeks, 4 days ago

    Hello @jigneshmpatel ,

    thanks for the fast and amazing help, it is working with your fix!

    Regards, M

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.