Library · Payment orchestration · How to run this
Gateway attempts can skew off the MID plan
Gateway attempts can skew off the MID plan. Actual % = gateway / total × 100. Skew % = |actual − plan|. Type gateway attempts, total attempts, and MID plan %.
Pair: Gateway attempt skew on Orchestration. Hops: failover auth count. Recycle: recycle vs cascade.
What you type
Gateway attempts — attempts on the gateway you are checking in the window.
Total attempts — all attempts in that same window (CRM / gateway export).
MID plan % — written share that gateway / MID was supposed to take.
Actual % = gateway / total × 100. Skew % = absolute gap vs plan. Rebalance routing when skew is material — do not invent a skew chip.
What not to do
Do not invent a skew percent. Do not mix recycle rows into gateway attempts without splitting. Do not treat hop count as plan %. Do not average every MID when one owns the skew.
Related: Orchestration, failover auth count, recycle vs cascade, fallback gateway share.
Procedure
- Type gateway attempts, total attempts, and MID plan %.
- Read skew %.
- Rebalance routing when skew is material.
Failure modes
- Inventing a skew percent.
- Mixing recycle rows into gateway attempts without splitting.
- Treating hop count as plan %.
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
- Gateway attempt skew %
- Absolute gap between gateway attempt share % and written MID plan %.
Work with us — We run this job on your accounts. Services
FAQ
- Is this failover auth count?
- Related hops. [Failover auth count](/manuals/failover-auth-count) is auths per order. This page is gateway attempt share vs a written MID plan %.
- Is this recycle vs cascade?
- Related CRM hops. [Recycle vs cascade](/manuals/recycle-vs-cascade) is recycle ladder vs cascade hops. This page is attempt skew vs MID plan.
- What skew % should I invent?
- None. Type gateway attempts, total attempts, and the written MID plan %.