Skip to article
ecomservices.io
Payment orchestration · How to run this
RoutingCalculatorCascadeCalculatorRetriesCalculator3DS placementCalculatorDeclinesCalculatorAffinityNot on this page yetOptimisationCalculator

Library · Payment orchestration · How to run this

Response mix is not MID plan skew

How to run thisPayment orchestration3 steps
CalculatorProcessor response skew · Calculator lives in the articleOpen

One response-code bucket can drift off the expected mix. Actual % = bucket ÷ total × 100. Skew % = |actual − expected|. Type all three.

Pair: Processor response skew on Orchestration. MID plan: gateway attempt skew. Soft/hard: campaign decline bucket.

Inputs

Bucket count — responses in the named processor code bucket (window).

Total responses — all processor responses in that same window.

Expected mix % — the share you expected that bucket to hold (typed).

Actual % = bucket ÷ total × 100. Skew % = absolute gap vs expected. Retune routing or BIN rules when skew is fat — leave blank chips alone.

Hard stops

Do not invent skew %. Do not treat MID plan share as expected response mix. Do not mix CRM unique declines into processor responses without splitting. Slice the hottest code first.

Related: Orchestration, gateway attempt skew, campaign decline bucket, soft vs hard decline.

Procedure

  1. Type bucket count, total responses, and expected mix %.
  2. Read skew %.
  3. Retune routing when skew % is material.

Failure modes

  • Inventing skew %.
  • Treating MID plan share as expected response mix.
  • Mixing CRM unique declines into processor responses.

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

Processor response skew %
Absolute gap between response-code bucket share and expected mix %.

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

FAQ

Is this gateway attempt skew?
Different grain. [Gateway attempt skew](/manuals/konnektive-gateway-attempt-skew) is attempt share vs MID plan. This page is one response-code bucket vs expected mix on Braintree responses.
Is this campaign decline bucket?
Sibling soft/hard split. [Campaign decline bucket](/manuals/sticky-campaign-decline-bucket) is soft vs hard shares. This page is skew of a named processor code bucket vs the mix you typed.
What skew % should I invent?
None. Type bucket count, total responses, and expected mix % from the same Braintree window.