I am trying to create a checkout using the StoreFront API, manage it by linking it to a user on our own service side, and use the checkout_url for payment.
It seems that the checkout.id returned by the StoreFront API does not match the checkout_id included in the order.
The gid retrieved by base64 decoding the checkout.id
and the token contained in checkout.checkout_url
and order.checkout_token seemed to match.
Is it okay to use order.checkout_token as the identification ID that links the checkout of the StoreFront API to the order of the Admin API?
(Because it's called a token, I thought it was some kind of one-time token, but is it okay to treat it as a persistent unique ID?
User | Count |
---|---|
13 | |
12 | |
7 | |
6 | |
5 |