Primer

primer.io ↗

Connect payment routing with transaction-level operational visibility

SI Score
80/100
Pricing
Contact for Pricing AI reading, not confirmed
Free plan
No AI reading, not confirmed
Sign-up required
Required AI reading, not confirmed

Ask SI about Primer

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Primer homepage

What it does

Primer provides payment orchestration, checkout, vault and operations tools for merchant payment teams. Businesses can connect existing processors and control how transactions move between services. A merchant account and signed order form are required; charges are set in that agreement, with a sandbox available for integration testing.

Start in Integrations on the Primer Dashboard and choose + New integration. Select a processor, connect its account using the requested credentials or authorization flow, and add the relevant merchant accounts. At least one processor must be connected before live payment processing.

Then open Workflows. A payment workflow can begin with the Payment created trigger and pass its payment identifier to an Authorize payment action using the chosen processor. Add conditions to select the appropriate route. Primer validates incomplete blocks before publishing; edits to a published workflow stay in a draft until you publish them again.

Inspect an actual Workflow Run to understand the result. Its timeline shows the route taken, and selecting a block reveals its inputs, outputs and requests. A completed workflow does not necessarily mean a paid order: a processor can decline a payment while the workflow itself finishes normally. Conversely, a later notification failure can mark the run unsuccessful after authorization has already succeeded. Check the payment timeline as well.

Compare those transaction results before changing rules for later traffic. The commercial order form sets the service fees and any minimum commitment, so include both expected volume and the required connections when discussing the contract.

Strengths

  • The sandbox starts with a preconfigured test processor.
  • Non-card methods can be enabled for individual processor merchant accounts and configured separately in Checkout.
  • Run metrics show how long individual steps took, including time spent waiting for customer authentication.

Watch out for

  • Only the first matching branch of a Conditions block is used.
  • Full production Workflow Run details are retained for 90 days; the payment timeline is separate.

Best for

  • Payment operations teams investigating routing and authorization outcomes
  • Merchants coordinating several processors through one checkout integration

Sources