Method
Which date, source, direction, and transformation produced the rate?
FX reference workflow
12 exchange-rate decisions to settle before using a number
Start with the decision behind the number. Each guide gives a short answer, conditional recommendation, limitations, source path, and reusable evidence workflow.
Three trust checks
Evidence
Can another reviewer reproduce the number from a URL, row, or API response?
Boundary
Is this reference data, an executed provider amount, or a rule imposed by an authority?
Start with your workflow
Open the decision that usually blocks your next step.
Finance and accounting
Preserve a dated rate, source, method, and review boundary for invoices, close, tax, or audit support.
Open workflowCross-border sellers
Separate the public reference rate from the bank, platform, or payment-provider amount actually received.
Open workflowDevelopers and internal tools
Choose JSON, CSV, or spreadsheet access and understand the public API boundary before integration.
Open workflowStablecoin receipts
Record the asset, timestamp, fiat reference, source URL, and limitations together.
Open workflowHow should USDT or USDC be recorded?
Keep the asset, timestamp, fiat reference, source URL, and limitations together.
Can FXpeek rates be used for tax or audit evidence?
FXpeek can help preserve dated reference-rate evidence, but it does not decide which rate a tax authority, auditor, or accounting policy requires. Confirm the required convention first, then save the date, pair, rate, source URL, and exported row together.
How do I preserve an audit trail?
Save the dated source URL, exported row, selected convention, and retrieval context.
Which daily exchange rate should I use for a dated record?
Start with the date required by the document or policy: invoice date for invoice recognition, payment date for cash settlement, or reporting date for period-end measurement. If the selected date has no published reference point, record the latest available business-day date rather than silently relabeling it.
Where did the number come from?
Review the source chain, update timing, latest available date, and reference-only method.
How does FXpeek handle Southeast Asian and long-tail currency pairs?
FXpeek publishes regional pair pages only when the underlying reference data is available and verifiable. Users should check the source date, pair direction, missing dates, inversion method, and intended reference-only use before relying on a series.
FXpeek vs XE vs OANDA for historical exchange-rate work
Choose by job, not by a universal winner. FXpeek is designed for lightweight dated-reference, source-URL, CSV, spreadsheet, and selected regional/stablecoin workflows. XE and OANDA offer broader commercial currency-data products; review their official coverage, licensing, frequency, and service terms when those requirements matter.
Reference exchange rate vs bank or payment-provider rate
A reference rate is a reproducible information point. A bank or payment-provider rate may include timing differences, spread, fees, liquidity, card-network rules, and customer-specific pricing. Use FXpeek for reference and evidence, and use the provider statement for the executed amount.
How far back does FXpeek historical exchange-rate data go?
Coverage varies by currency pair and upstream source. Check the pair page or API response for the actual available dates; do not assume every pair starts in the same year or updates on the same schedule.
Why is the FXpeek API free, and what are its limits?
FXpeek keeps lightweight public examples available for lookup, prototypes, spreadsheets, and evaluation. No fixed public daily allowance is promised on this page; abusive or high-volume traffic may be limited, and production users should monitor responses and request a managed workflow when continuity matters.
How hard is API or CSV integration?
Choose JSON, CSV, Google Sheets, or a public page according to the next workflow step.
A simple exchange-rate policy template for teams
A usable team policy states which business event selects the date, which reference source is used, how non-publishing days are handled, what evidence is saved, who approves exceptions, and when the policy is reviewed.