Focuses on API authentication, access scopes, and permission management.
Hello Team,
I'm trying to test the new Payments App. i'm getting the following error when doing a paymentsAppConfigure GraphQL mutation
{
"errors": [
{
"message": "Internal error. Looks like something went wrong on our end.\nRequest ID: 10ad0062-0716-442b-bb1f-02902b262a02 (include this in support requests).",
"extensions": {
"code": "INTERNAL_SERVER_ERROR",
"requestId": "10ad0062-0716-442b-bb1f-02902b262a02"
}
}
]
}
Contacted support by email, and they mentioned that i need both "write_payment_gateways" and "read_payment_gateways" scopes.
i already request both in my OAuth call. Scopes in OAuth:
scopes = ["write_payment_gateways", "write_payment_sessions", "read_payment_gateways", "read_payment_sessions"]
Don't know what to do, could you support?
Thanks
Solved! Go to the solution
This is an accepted solution.
Hey @dabedala
Thanks for raising this! I've been investigating this in the meantime and the request ID allowed me to identify some unexpected behaviour with thepaymentsAppConfigure
mutation.
A fix for this is being worked on, which we expect to push to production soon. In the meantime, you can continue to develop by sending an externalHandle
with thepaymentsAppConfigure
mutation.
I'll circle back here to let you know when it's shipped!
This is an accepted solution.
Hey @dabedala
Thanks for raising this! I've been investigating this in the meantime and the request ID allowed me to identify some unexpected behaviour with thepaymentsAppConfigure
mutation.
A fix for this is being worked on, which we expect to push to production soon. In the meantime, you can continue to develop by sending an externalHandle
with thepaymentsAppConfigure
mutation.
I'll circle back here to let you know when it's shipped!
Hey @dabedala
Just writing to you know this fix has now shipped - thanks!