Menu

Auditing a card-processing statement: expected vs billed, without guessing
📰

Auditing a card-processing statement: expected vs billed, without guessing

DEV Community: javascript·Tidy Cents·about 7 hours ago
#yFIiJdJU
#devtojavascript#devto#dev#rule#const
Reading 0:00
15s threshold

Link: https://gettidycents.com/product/merchant-fee-audit-switch-lab (paid tool, $29 one-time; the free demo uses fictional data)

A statement total is not something you can check against a headline rate. You check it rule by rule, charge by charge , and you keep anything you cannot explain apart instead of averaging it away.

// contract: 1.6% + $0.10 per payment (cents) const rule = { pct : 0.016 , fixed : 10 } ; const payments = Array ( 2000 ) . fill ( 4000 ) ; // 2,000 payments of $40

const expected = payments . reduce ( ( sum , amount ) => sum + Math . round ( amount * rule . pct ) + rule . fixed , 0 ) ; const billed = 163000 ; // what the statement says

console . log ( expected , billed - expected ) ; // 148000 15000 -> $1,480 expected, $150 to explain

Enter fullscreen mode

Exit fullscreen mode

That $150 is not an overcharge yet. Refunds, disputes, a monthly fee or a different card group can explain it.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.