You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 28, 2021. It is now read-only.
Hi, I'm having trouble matching the signature Shopify generates for a shop with the character "®" in it's shop name.
The signature I generate is: f45ce49a4dcf227d0935a3378129bb183eb50b6c73fbce00389b7e13cbb4a155 vs. the signature Shopify generate for the same response params which is: 7b61044affc253f0485f08c44f071a37c9535f3aedf4362bd5197725f0b39ddc
Please see the full request params below, ignore the slashes this is because I've stringified the json request body.
Where params is the request body and secret is the correct gateway secret for the shop. This is heavily tested and works across many shops, the same code works on this shop if ® is removed from the shops name.
I noticed the calculator https://offsite-gateway-sim.herokuapp.com/calculator is a bit outdated as it's fields are different to what Shopify POST's most notably shopify posts x_customer_shipping_first_name & x_customer_shipping_last_name but the calculator has billing first and last name fields instead of shipping so this is likely the cause of the calculator generating an entirely different result? Below is my request on the calculator the "secret_key" is there but it's cut off the bottom of the screenshot as wanted to keep it private. Note that I manually changed the billing first and last name fields to match the request from Shopify. It's given me the signature d8336dc1970dc5527cd1c9c5303ebf582c4be73c5bf8950098f08a683df9b5c1 which matches neither mine nor Shopify's.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I'm having trouble matching the signature Shopify generates for a shop with the character "®" in it's shop name.
The signature I generate is: f45ce49a4dcf227d0935a3378129bb183eb50b6c73fbce00389b7e13cbb4a155 vs. the signature Shopify generate for the same response params which is: 7b61044affc253f0485f08c44f071a37c9535f3aedf4362bd5197725f0b39ddc
Please see the full request params below, ignore the slashes this is because I've stringified the json request body.
I use the node.js crypto library to generate the signature like so:
Where
params
is the request body andsecret
is the correct gateway secret for the shop. This is heavily tested and works across many shops, the same code works on this shop if ® is removed from the shops name.I noticed the calculator https://offsite-gateway-sim.herokuapp.com/calculator is a bit outdated as it's fields are different to what Shopify POST's most notably shopify posts x_customer_shipping_first_name & x_customer_shipping_last_name but the calculator has billing first and last name fields instead of shipping so this is likely the cause of the calculator generating an entirely different result? Below is my request on the calculator the "secret_key" is there but it's cut off the bottom of the screenshot as wanted to keep it private. Note that I manually changed the billing first and last name fields to match the request from Shopify. It's given me the signature d8336dc1970dc5527cd1c9c5303ebf582c4be73c5bf8950098f08a683df9b5c1 which matches neither mine nor Shopify's.

The text was updated successfully, but these errors were encountered: