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

Spreedly orchestration hop wins on one gateway seat

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

Open one Spreedly orchestration hop export. Count hop wins. Divide by hop tries. Multiply by 100 for SP retry-success %.

Calculator: Retry-success share on Payments. Vault twin: Braintree retry-success. Outage twin: retry after outage.

Hop export

Hop wins — Spreedly orchestration reattempts that approved in the export.

Hop tries — Spreedly orchestration reattempts fired on that same gateway-seat export.

SP retry-success % = hop wins ÷ hop tries × 100. When SP retry-success % thins out, retune the hop schedule or gateway mix on that seat — do not invent a chip.

Hard stops

Leave SP retry-success % blank rather than invent. Keep Braintree vault CSVs out of Spreedly hop boxes. Keep outage-recovery rows out of the steady hop win count. Keep one Spreedly gateway seat per run when that seat owns the thin hop book.

Related: Payments, Braintree retry-success, retry after outage, soft-decline.

Procedure

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

Failure modes

  • Inventing SP retry-success %.
  • Loading Braintree vault hops into Spreedly boxes.
  • Treating outage-recovery rows as steady hop wins.

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

SP retry-success %
Retries that succeed ÷ retries attempted × 100 on one Spreedly gateway-seat hop window.

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

FAQ

Is this Braintree retry-success share?
Spreedly orchestration hop export vs Braintree vault recycle. [Retry-success share](/manuals/braintree-retry-success-share) stays on Braintree. Win / try totals never leave Spreedly here.
Is this Spreedly retry-after-outage?
Steady hop wins vs post-outage retries. [Retry after outage](/manuals/spreedly-retry-after-outage) scores recovery after downtime. Here you only score hop wins over hop tries on a normal seat.
What SP retry-success % should I invent?
None. Read hop wins and hop tries from the same Spreedly gateway-seat export.