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

Solidgate retry wins are not Primer retry wins

How to run thisPayments3 steps
CalculatorSolidgate retry-success share · Calculator lives in the articleOpen

Open one Solidgate retry seat. Count retries that succeed. Divide by retries attempted. Multiply by 100 for SG retry-success %.

Tool: Retry-success share under Payments. Neighbor on Primer: Primer retry-success. Cascade counterpart: cascade fail.

Seat columns

Retries that succeed — Solidgate retry hops that approved in the seat window.

Retries attempted — Retry hops attempted in that same Solidgate seat window.

SG retry-success % = retries that succeed ÷ retries attempted × 100. Thin SG retry-success % means retune route rules or BIN mix on that seat — blank chips stay blank.

Stops

Never invent SG retry-success %. Never mix Primer orchestration hops into Solidgate columns. Never treat cascade-fail or soft-decline piles as retry-success. Never fuse seats when one Solidgate MID owns the hole.

Related: Payments, Primer retry-success, cascade fail, soft-decline.

Procedure

  1. Type retries that succeed and retries attempted.
  2. Read SG retry-success %.
  3. Retune route rules when SG retry-success % is thin.

Failure modes

  • Inventing SG retry-success %.
  • Loading Primer orchestration hops into Solidgate boxes.
  • Treating cascade-fail piles as retry-success.

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

SG retry-success %
Retries that succeed ÷ retries attempted × 100 on one Solidgate retry seat.

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

FAQ

Is this Primer retry-success share?
Solidgate pay-rail seat vs Primer orchestration hop. [Retry-success share](/manuals/primer-retry-success-share) stays on Primer. Succeed / attempt totals never leave Solidgate here.
Is this Solidgate cascade fail share?
Retry wins vs cascade dies. [Cascade fail share](/manuals/solidgate-cascade-fail-share) scores cascade fails. Here you only score retries that succeed over retries attempted.
What SG retry-success % should I invent?
None. Read retries that succeed and retries attempted from the same Solidgate retry seat.