Error "Payments App doesn't exist." on calling paymentsAppConfigure merchant readiness API

7 0 2

We are creating a payment app to integrate a payment gateway on Shopify. One of the steps after finishing merchant onboarding is calling the paymentsAppConfigure GraphQL mutation to indicate to shopify that we are ready to process transactions for the merchant, as mentioned on this documentation page. However, we receive an error on the response to the API hit.

Description of error: "Payment App does not exist"

Documentation page for the paymentsAppConfigure API 

Curl for the request:

curl --location --request POST '' \
--header 'X-Shopify-Access-Token: exampmle_access_token' \
--header 'Content-Type: application/json' \
--header 'Cookie: request_method=POST' \
--data-raw '{
    "query": "mutation {  paymentsAppConfigure(externalHandle : \"example_readiness hit\" ,ready: true) {   paymentsAppConfiguration {      externalHandle      ready    }    userErrors {    field      message    }  } }",
    "variables": {}

 Response json:

    "data": {
        "paymentsAppConfigure": {
            "paymentsAppConfiguration": null,
            "userErrors": [
                    "field": null,
                    "message": "Payments App doesn't exist."
    "extensions": {
        "cost": {
            "requestedQueryCost": 10,
            "actualQueryCost": 10,
            "throttleStatus": {
                "maximumAvailable": 54600.0,
                "currentlyAvailable": 54590,
                "restoreRate": 2730.0

 We get the error - Payments App doesn't exist.

Any help on configuring the app for receiving payments will be appreciated. We have already created a version of the payments extension on the app, with various configurations and countries active. What else do we need to do here?

New Member
3 0 0

I am also seeing this. Did you get a resolution?

New Member
1 0 1

I had a similar issue, after chatting with support. You need to have published the Payments app before you can perform the testing.

See the requirements here:

New Member
3 0 0

For other, you need to have a version of the extension approved and published.

The app itself can remain in draft