The relationship
The job is usually catalog, payments, or POS. We open with that and an App Marketplace listing, not a generic payments deck (that is Stripe's door).
Square is a Commerce platform. Payments plus POS plus online, used by retailers who live in person and on the site. A technology partnership here is not a logo on a partners page. It is a named owner, a commercial motion a seller can explain, and a plugin, API, or workflow a customer can run. Merchants live in the store. A technology partnership here is an app they can install, a webhook they can trust, and a listing they can find. Distribution is the store’s marketplace, not your blog.
PartnerMatch would open this the same way we open every book: named overlap, a one-pager, then a scope. Read the developer docs before the first call. Use the relationship method if you want the order on one page.
App listing first. Referral from agencies and other apps. Plus or Enterprise co-sell after you have merchant proof. If Square has a take rate on a store, model it before you price the listing. A referral is the right first move for most B2B SaaS teams. Co-sell waits for a seller on their side who will attach you to a live deal.
Catalog, Orders, Payments, and webhooks. OAuth. We treat in-person and online as one catalog if the merchant does.
One merchant job: catalog, orders, checkout, or support. Pass app review. Then deepen. Put the listing, the help article, and the seller sentence on the same checklist as auth. A connector nobody can find is not a partnership.
Promising a Plus co-sell before the app is live. Building every object in v1. Ignoring review as a project with a date. On Square specifically: arriving without a workflow, asking for co-sell before anything is installed, and treating Square App Marketplace for apps.
Aspiring partner managers: the Academy lessons platform programs, marketplace listings, and scoping for non-engineers are the class. Companies that want the channel built book a Partner Audit.
The job is usually catalog, payments, or POS. We open with that and an App Marketplace listing, not a generic payments deck (that is Stripe's door).
Catalog, Orders, Payments, and webhooks. OAuth. We treat in-person and online as one catalog if the merchant does.
We do not invent names. Square assigns a partner manager after you are in the program. The seats to look for:
Square App Marketplace for apps. Broader partnerships for platforms embedding Square. Pick one.
People move. Verify on the partner program page before you write to anyone.
Start from the official program, not a cold note to a VP. Read Square’s partner page. Square App Marketplace for apps. Broader partnerships for platforms embedding Square. Pick one. PartnerMatch opens with named shared customers and a scoped workflow, then the listing if there is a store.
Ship one job, not a platform rewrite. On Square that usually means: Catalog and inventory. One merchant job: catalog, orders, checkout, or support. Pass app review. Then deepen.
Yes. List there as part of launch, not as an afterthought. The store is how their customers find you after the first install. Official listing: Square marketplace.
We do not invent names. Look for App Marketplace partner manager; Strategic partnerships for platforms. Square App Marketplace for apps. Broader partnerships for platforms embedding Square. Pick one.
This page is independent. PartnerMatch is not affiliated with Square. Program terms change. Read them on the official pages above before you commit engineering. Last reviewed August 2026.
A Partner Audit maps the partners worth building, the commercial motion, and the integration that has to ship. Then we run it with you.
Book a Partner Audit