Primer

Primer's pitch is that finance and payments teams should see every transaction and be able to act on it. The merchant terms are issued by Primer API Limited, governed by English law, with the courts of England and Wales as venue.

Its product pages group the platform into three jobs: accepting payments with a checkout and vault, optimising them with workflows and fallbacks, and managing them with monitors, reconciliation and a costs view.

Workflows without a release cycle

The workflow builder lets a payments team define which processor handles which payment, and what happens on a failure, without touching code. Fallbacks route a payment to a secondary processor when the first one fails.

This suits teams where routing changes are waiting in an engineering backlog.

Vault and credentials

Primer positions its centralised vault as one place to unify and manage every payment credential. For an orchestration buyer the key question is portability: ask how tokens can be exported if you leave.

The vendor's terms are the document to read for this, since they govern the data relationship.

Visibility across providers

Monitors track payment metrics across all providers in real time, and a costs overview aims to expose fee leakage and benchmark providers. Customer stories on the site include Printify and Lime.

Those pages are vendor-selected, so treat them as illustrations rather than benchmarks.

Limitations to Consider

No public pricing; the pricing page is not available and contact is by demo request. The founding year and headcount were not found on its pages. Primer is a UK company, so it falls outside the EU even though it is European. For a German alternative with a Merchant of Record option see Payrails.

Who Should Use Primer

Product and payments teams at online merchants who run several processors and want rules, vaulting and reconciliation in a single UK-contracted platform.