Resources · 94

Commerce: verify currency amounts and rounding

Reconcile displayed prices, orders, payments and refunds without mixing units.

· 9 min

Fictional empty analysis laboratory: three brass blocks, blank dial, ledger sheets and burgundy folder AI-generated editorial illustration

What this guide helps achieve

  • Attach currency to amount
  • Follow provider units
  • Separate calculation and display
  • Specify rounding policy
  • Reconcile every output

Quick check

  • Do all currencies use two decimals?
  • Does Intl.NumberFormat calculate price?
  • How should a leftover cent be assigned?

Step-by-step method

  1. 01

    Attach currency to amount

    Store value and currency code together. Distinguish presentment from settlement currency. Never sum euros and yen; conversion needs an explicit rate, date and rule.

    Output: Amounts paired with currency.

  2. 02

    Follow provider units

    Stripe expects amounts in the unit defined for each currency. Check exceptions. Its examples use 1099 for 10.99 USD and 10 for 10 JPY. Do not universally multiply by 100.

    Output: Unit contract per operation.

  3. 03

    Separate calculation and display

    Use exact decimal representation or integers suitable for the contract. Localised formatting does not establish the reference value. A displayed string with separators is not a reliable technical amount.

    Output: Separate exact values and display.

  4. 04

    Specify rounding policy

    Document line or total rounding, discount allocation and residuals. Validate tax and document rules for the applicable context. Replay quantities, partial refunds and edge cases without silently switching policy.

    Output: Rounding policy and edge cases.

  5. 05

    Reconcile every output

    Compare currency, units, totals and identifiers across basket, order, notification, invoice and refund. Check amounts server-side. A correctly formatted screen can conceal an incorrect payment request.

    Output: Reconciliation across systems.

Fictional acceptance-test scenarios

These proposed cases are not client observations. Adapt data, permissions and acceptance criteria to your authorised environment.

Situation to exerciseResult to checkEvidence to retain
Three lines each have a fictional pre-rounding amount of 0.335.Define precision and the applicable rule before comparing rounded-line sums with a rounded total; do not select rules to obtain a preferred outcome.Exact amounts, operation order and documented rule.
An API receives an amount in another currency.Check currency, expected unit and provider exceptions; do not universally multiply by 100.Payment contract and a payload without sensitive data.
Two partial refunds concern the same capture.Reconcile confirmed amounts, currency and history to prevent over-refund or duplication.Stable identifiers, states and confirmed refunded total.

Acceptance case to reproduce

Fictional example: these inputs describe no customer or observed result.

View case inputs
{
    "currency": "JPY",
    "display_amount": 1000,
    "stripe_amount": 1000,
    "incorrect_times_100": 100000
}

Expected decision

For JPY 1,000, the Stripe amount is 1000. Do not multiply every currency amount by 100.

Verification procedure

  1. Record currency and the provider’s expected unit.
  2. Test JPY and a two-decimal currency.
  3. Keep comparisons of stored, displayed and rounded amounts.

Stripe — Currency amounts

Reusable worksheet

Complete with your authorised observations. These fields are a working template, not observed results.

FieldInformation to record
AmountExact value, currency and unit
CalculationQuantities, discounts, tax and rounding
PaymentContract, submitted and received amounts
AcceptanceDifferences, edge cases and refunds

Worked example

Illustrative situation

Fictional EUR example: splitting €10.00 into three €3.33 lines leaves one cent unallocated.

Decision and expected evidence

The selected rule assigns that cent to a defined line and preserves a €10.00 total. This is not a universal tax rule.

Distinguish the mechanisms

MechanismPurposeCheck or limitation
Calculation valuePerform an exact operationDocument precision and rounding
API amountFollow provider contractCurrency-specific unit
Localised displayPresent amount and symbolNot an accounting calculation

Management indicators

IndicatorWhat it measuresFirst action
Total discrepanciesDifferences between systemsReconcile before confirmation
Currency casesSupported currenciesTest each distinct contract
ResidualsAllocation differencesApply documented policy

Common pitfalls

  • Document precision and rounding
  • Currency-specific unit
  • Not an accounting calculation

Frequently asked questions

Do all currencies use two decimals?

No. Check current provider contract and currency rules, including operation-specific exceptions.

Does Intl.NumberFormat calculate price?

It formats a value. Define calculation, taxes, discounts and rounding beforehand.

How should a leftover cent be assigned?

Use a validated, reproducible allocation rule. Retain the reference total and line breakdown.

API amount precision and exact units

A displayed value, a calculation amount and an API integer have different roles. This addition makes decimal scale, multiplier and required step explicit. The reader checks an exact representation before multiplying by quantity; it never silently rounds excess precision.

Adyen and Stripe documentation reviewed on 6 November 2026. Nine limited profiles explain unit contracts; this is neither a complete currency directory nor a list of available payment methods. Amounts and scenarios are fictional CIE examples.

Nine profiles: currency, operation and unit together

Nine profiles: currency, operation and unit together
ProfileDocumentary scopeRepresentation decimals eMultiplier 10ᵉRequired integer stepFictional example
Adyen · EURMinor-unit APIs, excluding Terminal API2100110.99 → 1099
Adyen · JPYMinor-unit APIs, excluding Terminal API011500 → 500
Adyen · KWDMinor-unit APIs, excluding Terminal API3100010.123 → 123
Stripe · ISKISK amount representation; fractional ISK not permitted21001005 → 500; 5.25 rejected
Stripe · UGXUGX charges; fractional UGX not permitted21001005 → 500; 5.25 refused
Stripe · HUF · chargeHUF charges2100110.45 → 1045
Stripe · HUF · payoutManual HUF payouts; whole currency amounts required210010010 → 1000; 10.45 refused
Stripe · TWD · chargeTWD charges21001800.45 → 80045
Stripe · TWD · payoutManual TWD payouts; whole currency amounts required2100100800 → 80000; 800.45 refused

The three Adyen profiles follow its decimal table for minor-unit APIs, excluding Terminal API. Stripe retains two-decimal representation for ISK and UGX while prohibiting fractions: the integer must be divisible by 100. For HUF and TWD, Stripe distinguishes two-decimal charges from manual payouts, which require an integer divisible by 100. Always select the operation profile; currency decimal count alone is insufficient. No exchange rate is described.

Adyen · Currency codes and minor units · Provider documentation · reviewed 2026-11-06

Stripe · Supported currencies and special cases · Provider documentation · reviewed 2026-11-06

Exact amount representation workshop

Select a profile, unit amount and quantity. Results show multiplier, step, unit integer, total integer and fixed decimal representations. Arithmetic uses exact integers; floating-point sums never determine the result. Extra decimal zeroes are accepted only when they do not change the value.

Workshop input profile: nonnegative amount with 1–12 digits before the point and 0–6 after it; ASCII point, no spaces, sign, grouping separator, exponent or redundant leading zeroes. Integer quantity 1–99 without leading zeroes. These educational bounds are not Adyen or Stripe limits.

No payment, API request, currency exchange, import, storage or export is performed. Exact representation establishes neither payment-method availability, minimum or maximum compliance, amount authorisation nor invoice compliance. This reader covers no tax, discount, negative refund, exchange, fee, settlement or applicable rounding rules.

A reviewable conversion path

A reviewable conversion path
StepCheck
1 · Read the stringSeparate integer and fraction without converting the value to floating point. Localised display strings require a separate explicit parser.
2 · Apply scale ePad the fraction to e. Beyond e, accept zeroes only; any extra nonzero digit causes a precision rejection.
3 · Check the stepThe resulting integer must be divisible by the profile step. Correct scale can still represent a prohibited value, such as fractional ISK in the Stripe profile.
4 · Multiply exactlyInteger total = unit integer × quantity. Reinsert the point e places from the end for technical representation; this is not a localised customer display.

Three rounding experiments separate from exact conversion

These fictional CIE calculations explicitly choose nearest rounding with ties upward, on nonnegative values only, to two decimals. This is an exercise convention, not a rule attributed to either provider. In a two-decimal profile, the interactive reader rejects these fractions rather than applying this convention.

Three rounding experiments separate from exact conversion
Exact amount × quantitySum of rounded linesRounded exact totalLines minus total
0.335 × 30.34 × 3 = 1.021.005 → 1.01+0.01
0.005 × 20.01 × 2 = 0.020.010 → 0.01+0.01
0.3333 × 30.33 × 3 = 0.990.9999 → 1.00−0.01

A rounding difference shows a different operation order; it does not by itself identify the legally or commercially correct result. Define the rule before calculation and retain the reference total and any residual allocation.

Twelve explained scenarios, available without JavaScript

M01 · Two decimals, three units
Two decimals, three units
Profile / amount / quantityExpected reading
adyen-eur / 10.99 / 31099 minor units per item; total 3297, or 32.97 EUR.
M02 · JPY without multiplying by 100
JPY without multiplying by 100
Profile / amount / quantityExpected reading
adyen-jpy / 500 / 2500 representation units per item; total 1000, or 1000 JPY.
M03 · Three KWD decimals
Three KWD decimals
Profile / amount / quantityExpected reading
adyen-kwd / 0.123 / 3123 minor units per item; total 369, or 0.369 KWD.
M04 · Unrepresentable JPY fraction
Unrepresentable JPY fraction
Profile / amount / quantityExpected reading
adyen-jpy / 10.5 / 1Precision rejection: 10.5 does not silently become 10 or 11. No integer amount is produced.
M05 · No implicit rounding
No implicit rounding
Profile / amount / quantityExpected reading
adyen-eur / 10.995 / 1Precision rejection: this exact reader selects no rounding rule for the third decimal.
M06 · ISK: scale and step differ
ISK: scale and step differ
Profile / amount / quantityExpected reading
stripe-isk / 5 / 25 ISK is represented as 500; two units produce 1000, or 10.00 in the two-decimal technical representation.
M07 · ISK: two decimals are insufficient
ISK: two decimals are insufficient
Profile / amount / quantityExpected reading
stripe-isk / 5.25 / 1Step rejection: this would represent fractional ISK. The contract requires an integer divisible by 100.
M08 · Display comma rejected
Display comma rejected
Profile / amount / quantityExpected reading
adyen-eur / 10,99 / 1Technical input rejected. Only the ASCII decimal point is accepted; the reader does not infer a locale.
M09 · Large integer preserved exactly
Large integer preserved exactly
Profile / amount / quantityExpected reading
adyen-kwd / 999999999999.999 / 99Integer total 98999999999999901, or 98999999999999.901 KWD. Arithmetic demonstration: this exceeds JavaScript Number safe integer precision and establishes no permitted API limit.
M10 · Exact zero, no eligibility inferred
Exact zero, no eligibility inferred
Profile / amount / quantityExpected reading
adyen-eur / 0.000 / 1Arithmetic conversion 0, representation 0.00. This does not establish acceptance of a zero payment.
M11 · Extra zeroes without loss
Extra zeroes without loss
Profile / amount / quantityExpected reading
adyen-jpy / 10.000 / 3Extra decimals are all zero: exact conversion 10; total 30 JPY.
M12 · Noncanonical quantity rejected
Noncanonical quantity rejected
Profile / amount / quantityExpected reading
adyen-eur / 10.99 / 03The CIE input profile requires an ASCII integer from 1 to 99 without leading zeroes. This syntax rejection is not a provider payment rule.
M13 · UGX: representation multiplied by 100
UGX: representation multiplied by 100
Profile / amount / quantityExpected reading
stripe-ugx / 5 / 15 UGX is represented by 500, with a step of 100.
M14 · Fractional UGX refused
Fractional UGX refused
Profile / amount / quantityExpected reading
stripe-ugx / 5.25 / 1525 fits the scale but is not divisible by 100; the fractional UGX amount is refused.
M15 · HUF: two-decimal charge
HUF: two-decimal charge
Profile / amount / quantityExpected reading
stripe-huf-charge / 10.45 / 110.45 HUF gives 1045 for a charge.
M16 · Same HUF, different manual payout
Same HUF, different manual payout
Profile / amount / quantityExpected reading
stripe-huf-payout / 10.45 / 11045 is not divisible by 100; this value is refused for a manual payout.
M17 · Whole-currency manual HUF payout
Whole-currency manual HUF payout
Profile / amount / quantityExpected reading
stripe-huf-payout / 10 / 110 HUF gives 1000, divisible by 100.
M18 · TWD: two-decimal charge
TWD: two-decimal charge
Profile / amount / quantityExpected reading
stripe-twd-charge / 800.45 / 1800.45 TWD gives 80045 for a charge.
M19 · Same TWD, different manual payout
Same TWD, different manual payout
Profile / amount / quantityExpected reading
stripe-twd-payout / 800.45 / 180045 is not divisible by 100; this value is refused for a manual payout.
M20 · Whole-currency manual TWD payout
Whole-currency manual TWD payout
Profile / amount / quantityExpected reading
stripe-twd-payout / 800 / 1800 TWD gives 80000, divisible by 100.

Test the monetary contract end to end

Test the monetary contract end to end
Suggested checkUseful record
ScopeProvider, API, operation, documentary version and currency. Do not extend a charge rule to every payout.
Reference valueExact amount linked to currency code; separate calculation unit, technical integer and presentation.
PrecisionBoundary cases, unrepresentable fractions, zeroes and integers beyond floating-point safe integer precision.
RoundingRule and application stage; compare line, total and allocation without changing conventions after observation.
ReconciliationValues and identifiers across order, request, confirmation and refund; also check server-side.
EligibilitySeparately verify current account, payment-method and operation constraints before any real transaction.

Investigate differences by retaining currency, unit and operation first. A correct symbol is insufficient: 500 may represent 500 JPY in one profile and 5 ISK in another. Exact representation and provider acceptance are complementary checks.

Sources and credits

Original CIE educational synthesis and calculations. Adyen and Stripe publish their respective documentation; no affiliation, certification or transaction guarantee is claimed. Fictional amounts are neither statistics nor client results. Recheck the current contract before a real integration.

Adyen · Currency codes and minor units · Provider documentation · reviewed 2026-11-06

SHA-256 : 558887aab2082ea9c937bdd1ec67eb27a3fd30098eda21107dea40a0d7f4beb0

Stripe · Supported currencies and special cases · Provider documentation · reviewed 2026-11-06

SHA-256 : e64bb9ab65e88a94c94fcc7bd8df1c1426d879e8020e7b2cc044b26bb6672929

Official references

References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.