• Payments app lifecycle
  • Next steps

Get approved for payments

Note

Our payments platform is available by invitation only while we continue to build out our Payments Apps API. Shopify will open the payments platform to new applications in the future.

Before a payments extension can be approved on Shopify’s payments platform, three reviews are required:

  • Payments Partner application review
  • Payments extension review
  • Payments app review

Payments Partner application review

Anchor link to section titled "Payments Partner application review"

  1. The Partner applies to become a Payments Partner.

    Partners should take time to review the “Additional Terms Applicable to Payments Developers” section of the Shopify Partner Program Agreement. If you aren't a Shopify Partner yet, then you must sign up to be a Partner.

  2. We grant the Partner access to build a payments extension.

    If you've been approved to be a Payments Partner, then you'll be granted access to Shopify’s payments ecosystem. You'll need to sign a revenue share agreement, which we provide in an email when you're approved.

  3. The Partner creates a new app in Shopify CLI.

Note

Payments extensions must adhere to technical requirements and provide a high-quality merchant experience as described in the minimum product requirements.

A flow chart of the Payments Partner application review process steps listed above

Payments extension review

Anchor link to section titled "Payments extension review"

  1. The Partner creates and configures the payments extension.

  2. The Partner submits the payments extension for review.

  3. We review the payments extension.

  4. If the app extension is approved, then the Partner can publish the extension.

    Note

    Publishing the app extension isn't the same as approving and publishing the app itself. Before you can publish your app and have it be able to process payments, the app needs to go through the app review process for final approval. For more information on the difference between an app and an extension, refer to app extensions.

  5. The Partner selects a distribution method for the app in the Partner Dashboard.

  6. The Partner tests the payments extension on a development store.

If we reject your payments app extension, then we'll send you an email indicating next steps. Make sure that you check the business email for your Partner account, as well as the email address included in your Payments Platform application. After making the required changes, you can resubmit your app extension.

A flow chart of the payments extension review process steps listed above

Payments app review

Anchor link to section titled "Payments app review"

Before this step of the review process, you must sign the payments app revenue share agreement. The link to the agreement is included in your payments platform application acceptance email. If you're unable to locate the agreement, then contact Partner Support. If you submit your app for review before you sign and submit the revenue share agreement, then your app will be rejected.

  1. The Partner submits the app for review.

  2. We review the app.

  3. If we approve the app, then the Partner can publish the app. Refer to onboarding a merchant to a payments app to learn about ways that a merchant can discover your payments app.

  4. Optional: If the app needs to be changed before it can be approved, then the Partner reconfigures the payments app extension and submits a new version of the payments app extension for approval.

A flow chart of the payments app review process steps

Payments app lifecycle

Anchor link to section titled "Payments app lifecycle"

A payments apps can go through four states. Each of these states defines by whom and how your app can be installed, and the general visibility of the app for merchants.

  • Development: The default state of a payments app is Development, after your first extension version is approved and published. The payments app can then be installed on dev stores for testing purposes.
  • Hidden: The payment app enters Hidden state after the app is approved and published by the app review team. The payments app isn't discoverable to merchants through the admin, but can now be installed by merchants by sharing the installation URL available in your dashboard.
  • Generally Available: The payments app enters Generally Available state by request if it meets certain criteria, such as being used by at least 50 Shopify stores and has processed over 1,000,000 USD. The payments app is now discoverable from the store admin as an alternative payment provider for all merchants in supported countries. It will also appear in the public payments brochure.
  • Not Installable: If the payments app fails to meet the minimum product requirements, it will be put into Not Installable state. In this state, the app isn't discoverable to merchants through the admin. The installation URL is removed from your dashboard, and it cannot be used for installation. The app can't be installed on any new shop, but shops that had the app installed previously will still be able to use it.
Development Hidden Generally Available Not Installable
Visible as an alternative payments provider? only on dev stores only if installed yes only if installed
Can process payments? only in test mode yes yes yes
Has an installation URL? no yes yes no
Visible on Shopify.com? no no yes no

You can view the state of your payments extension in the App section of the Partner Dashboard by clicking Edit draft next to your payments extension.

Screen showing the payments app state

Next steps

Anchor link to section titled "Next steps"
  • Learn how to Build a credit card payments extension

On this page

  • Payments app lifecycle
  • Next steps