Skip to article
ecomservices.io
Payments · How to run this
LedgerReconNot on this page yetFeesCalculatorSettlementCalculatorReservesCalculatorStatementsEntitiesNot on this page yetCommerce reconNot on this page yet

Library · Payments · How to run this

Primer routed hard kills are not Braintree hard kills

How to run thisPayments3 steps
CalculatorPrimer hard-decline share · Calculator lives in the articleOpen

Pull one Primer orchestration workflow export. Count routes tagged do-not-retry / hard. Divide that count by every decline row in the file. The quotient × 100 is PR hard-decline %.

Pair: Hard-decline share on Payments. Processor twin: Braintree hard. Soft twin: Primer soft.

Workflow math

Do-not-retry routes — Primer decline lines the workflow marks hard / do-not-retry in that export.

Full decline file — Every Primer decline row in the same workflow export (soft plus hard).

PR hard-decline % = do-not-retry routes ÷ full decline file × 100. A high PR hard-decline % means that workflow is burning cards that will not retry — move volume or fix the offer; leave blank chips alone.

Guardrails

Do not invent PR hard-decline %. Do not park soft-only lines in the do-not-retry count. Do not paste a Braintree vault decline file into Primer fields. Do not merge workflows when one Primer merchant owns the hard mix.

Related: Payments, Braintree hard, Primer soft, void fail.

Procedure

  1. Type hard declines and all declines.
  2. Read PR hard-decline %.
  3. Cut hard burns when PR hard-decline % is material.

Failure modes

  • Inventing PR hard-decline %.
  • Loading soft-only counts into the hard pile.
  • Folding Braintree decline rows into Primer boxes.

Worked example

None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.

Glossary

PR hard-decline %
Hard routes ÷ whole decline export × 100 on one Primer workflow.

Work with us — We run this job on your accounts. Services

FAQ

Is this Braintree hard-decline share?
Orchestration workflow vs Braintree vault. [Hard-decline share](/manuals/braintree-hard-decline-share) stays on Braintree. Route / file totals never leave Primer here.
Is this Primer soft-decline share?
Do-not-retry pile vs retryable pile. [Soft-decline share](/manuals/primer-soft-decline-share) stays on soft codes. This page only scores hard routes over the full Primer decline file.
What PR hard-decline % should I invent?
None. Source do-not-retry routes and the full decline file from the same Primer workflow.