For a merchant commissioning a multilingual checkout, a correct price label is only half the handover. Agree the currency, operation and integer amount sent to the payment provider. A universal “multiply by 100” helper can make a yen price one hundred times too large.
Primary evidence and claim boundaries
Stripe documents minor-unit amounts, zero-decimal currencies and operation-specific exceptions. These are separate from currency conversion. Primary reference · Read 17 October 2026.
Filled acceptance example
Synthetic teaching scenario, not a client case, provider integration test or business result. Scroll the example table on narrow screens.
| Approved input | Operation and basis | Expected handover |
|---|---|---|
| AUD 12.34 | Charge; 2 decimals | amount=1234, currency=aud |
| JPY 1234 | Charge; zero decimals | amount=1234, not 123400 |
| TWD 800.45 | Manual payout special case | 80045 is not divisible by 100; do not silently round |
| Unknown currency or operation | No approved conversion rule | Stop with explicit unsupported result |
Practical handover procedure
- Record a decimal string and ISO currency code in the brief; keep charge, refund and payout fields distinct. Use integer arithmetic or an audited decimal library, not floating-point guessing.
- Give the supplier the four rows above and a deliberately wrong JPY payload. Require a visible rejection for unsupported combinations and an explicit rounding policy where one is needed.
- In an authorised test environment, compare the displayed total, stored order amount, submitted minor units and provider record. Redact identifiers and retain the operation/version.
Interpret the outcome
The first two rows intentionally produce the same integer for different prices and currencies. The integer alone cannot reconcile an order. Carry currency and operation through exports, refunds and accounting handovers; never merge records on amount alone. The TWD row is a stop decision, not a recommendation to pay out a rounded balance.
Acceptance decision
Accept only after the supplier demonstrates both valid representations and rejection of the deliberately invalid cases. A screenshot of a formatted price does not satisfy the contract.
Limits and unverified work
Synthetic arithmetic only. No payment, payout, tax, exchange-rate or fee calculation was executed. Currency availability and provider limits depend on the actual account and payment method.
Download the filled bilingual acceptance record — Contains these inputs, steps, expectations and limits. This is a teaching record, not an executable integration.