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

Braintree hard kills are not Authorize.net hard kills

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

Open one Braintree merchant decline export. Count rows tagged hard / do-not-retry. Divide by every decline row in that export. That percentage is BT hard-decline %.

Pair: Hard-decline share on Payments. Gateway twin: Authorize.net hard. Soft twin: Braintree soft.

Merchant export

Hard rows — Braintree decline lines the processor marks hard / do-not-retry in the export.

Whole decline export — Soft plus hard Braintree decline lines in that same merchant file.

BT hard-decline % = hard rows ÷ whole decline export × 100. When BT hard-decline % climbs, stop retrying those cards and fix the offer mix — leave blank chips alone.

Stops

Skip inventing BT hard-decline %. Skip parking soft-only lines in the hard count. Skip dumping an Authorize.net gateway file into Braintree fields. Skip blending merchant accounts when one Braintree MID owns the hard mix.

Related: Payments, Authorize.net hard, Braintree soft, void fail.

Procedure

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

Failure modes

  • Inventing BT hard-decline %.
  • Loading soft-only counts into the hard pile.
  • Folding Authorize.net decline rows into Braintree 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

BT hard-decline %
Hard declines ÷ all declines × 100 on one Braintree merchant export.

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

FAQ

Is this Authorize.net hard-decline share?
Processor vault vs Auth.net gateway. [Hard-decline share](/manuals/authorize-net-hard-decline-share) stays on Authorize.net. Hard / export totals never leave Braintree here.
Is this Braintree soft-decline share?
Do-not-retry vs retryable. [Soft-decline share](/manuals/braintree-soft-decline-share) stays on soft codes. Here you only ratio hard rows against the whole Braintree decline export.
What BT hard-decline % should I invent?
None. Source hard rows and the whole decline export from the same Braintree merchant account.