A customer may receive a transfer quote now, fund the transaction minutes later, and have the recipient paid at another point in time.
Meanwhile, the underlying currency relationship can change.
Remittance Services
Build Clearer FX Workflows for Cross-Border Transfers
Reliable FX reference data is a core input for cross-border transfer pricing, rate monitoring, and reconciliation.
FinFeedAPI Currencies API provides current VWAP-24H reference exchange rates and historical currency data for supported currency pairs and assets, giving remittance platforms a consistent data layer across their FX workflows.
A Transfer Can Outlive the Rate Used to Quote It
Biggest Pain Points
Quotes have a time dimension
A rate shown to the sender cannot automatically remain valid indefinitely.
Send and receive amounts need a clear relationship
Users need to understand how the platform moved from the amount sent to the amount expected on the other side.
Fees and FX adjustments can become mixed together
Without a clear pricing model, customers may struggle to distinguish the reference exchange rate from the provider's fees, spread, or markup.
Different corridors behave differently
A remittance provider may need to manage many supported currency pairs, each with its own operational and pricing considerations.
Historical decisions need context
When investigating a transfer later, teams need both their own stored transaction records and relevant historical currency data rather than today's exchange rate.
From “Send 1,000” to “Recipient Gets X”
Consider a customer sending money from one currency into another.
The remittance platform may need to determine:
Reference rateWhat is the current VWAP-24H reference exchange rate for the supported pair?
Customer rateWhat executable or customer-facing conversion rate will the provider offer?
PricingDoes the provider apply a spread, markup, buffer, or other adjustment?
FeesWhich transfer fees are charged separately from the FX conversion?
Quote validityHow long will the provider honor the quoted send and receive amounts?
Funding and payoutWhat happens if the market changes before the transfer is funded, converted, or paid out?
A live reference rate does not itself create a locked customer quote or guarantee an executable conversion or payout rate.
How Does FinFeedAPI Solve It?
Establish a Consistent FX Reference
FinFeedAPI provides current VWAP-24H reference exchange rates calculated using a defined methodology. Remittance systems can use these observations as market-data inputs when generating quotes, evaluating supported currency relationships, or maintaining internal FX workflows.
Monitor Reference Rates While Quotes Are Active
WebSocket access can stream live exchange-rate updates based on the Currencies API exchange-rate methodology. A remittance provider can monitor how the reference data changes while applying its own rules for quote expiration, repricing, buffers, or rate locks.
These updates should not be interpreted as raw tick-by-tick executable venue quotes. FinFeedAPI also does not determine whether a quote should change or guarantee the rate at which a transfer can be executed or settled.
WebSocket is intended for live data. Historical investigation and reconciliation can use supported historical access through REST, JSON-RPC, or MCP.
Separate the Reference Rate From Customer Pricing
A reference exchange rate and the rate offered to a customer are different concepts. Providers can use FinFeedAPI as the reference-data layer while separately applying their own spreads, fees, margins, buffers, and corridor-specific pricing rules. This makes it possible to keep the underlying currency reference distinct from the provider's commercial pricing methodology.
Reconstruct Historical FX Context
Historical point-in-time exchange rates using the VWAP-24H methodology allow teams to examine currency observations from earlier periods. These observations can support transfer investigations, reconciliation, dispute research, and refund analysis. They do not prove which rate was quoted, accepted, executed, or settled for a particular transaction. The provider's stored quote and transaction records remain necessary for that purpose.
Analyze Currency Relationships Over Time
Historical OHLC exchange-rate timeseries can help teams study how supported currency and asset pairs moved across different periods. That information can support corridor analysis, treasury research, pricing reviews, and internal FX-risk research.
Follow the FX Reference Through the Transfer Lifecycle
1. Build a Transfer Quote
Retrieve the current VWAP-24H reference exchange rate for a supported currency pair. The remittance platform can use that reference as one input when calculating its own customer-facing conversion rate, fees, spread, rounding, and send/receive amounts.
2. Define a Quote Window
Record when the customer quote was created and how long the provider intends to honor it. If the customer acts after that window, the application can retrieve updated reference data and apply the provider's own requoting policy.
3. Monitor Currency Movement
WebSocket can stream live exchange-rate updates for supported workflows. Backend systems can observe how the VWAP-24H reference changes while transfers or quotes are active. Whether that information affects an existing quote depends entirely on the provider's pricing and rate-lock rules.
4. Execute the Transfer
Funding, executable FX conversion, liquidity sourcing, payment processing, settlement, and payout are handled by the remittance provider and its financial infrastructure. FinFeedAPI remains the reference currency-data layer.
5. Reconcile the Transaction
The provider should retain the internal quote, customer rate, fees, timestamps, transaction details, and other records required by its reconciliation process. Historical FinFeedAPI currency data can provide supporting market context for that process, but it is not evidence of the actual rate offered to or executed for the customer.
6. Investigate Historical Transfers
If a transfer is questioned later, teams can retrieve historical point-in-time exchange-rate data for the relevant period and compare it with their own stored quote and transaction records. This creates a clearer distinction between what the reference currency data showed and what the provider actually quoted and executed.
Different Stages Need Different Currency Data
| Capability | Role in Remittance | Example |
|---|---|---|
| Current VWAP-24H Reference Exchange Rates | Market-data input for transfer quoting | Retrieve a current reference for a supported send/receive currency pair |
| Historical Point-in-Time VWAP-24H Rates | Historical FX context | Examine the reference exchange rate around an earlier transfer |
| Historical OHLC Exchange-Rate Timeseries | Corridor and FX-movement analysis | Study exchange-rate movements across supported periods |
| REST | On-demand live and historical requests | Retrieve reference data when creating a quote or reviewing a historical transfer |
| WebSocket | Streaming live exchange-rate updates | Monitor changing VWAP-24H reference data in backend services |
| JSON-RPC | RPC-style live and historical access | Integrate supported currency resources into transfer and analytical services |
| MCP | Structured access to supported currency tools | Connect compatible AI-assisted workflows to supported Currencies API resources |
Historical OHLC exchange-rate data is available across supported candle periods from 1SEC through 10DAY. Currencies API supports fiat currencies and digital assets. Remittance providers should verify that the specific currency or asset pairs required for their corridors and workflows are supported.
From a Rate Lookup to a Traceable FX Reference Workflow
| Transfer Requirement | Without a Defined Currency-Data Layer | With FinFeedAPI |
|---|---|---|
| Quote reference | Reference data may come from different or manually maintained sources | Current VWAP-24H rates provide a consistent reference methodology |
| Live monitoring | Currency monitoring may require separate integrations | WebSocket can stream live exchange-rate updates |
| Customer pricing | Reference rates, spreads, and fees may be difficult to separate internally | Teams can keep reference data separate from their own executable pricing logic |
| Quote expiration | Repricing may operate without a consistent updated reference | Applications can retrieve updated reference data when their own quote policy requires it |
| Historical investigation | Today's rate provides little context for an older transfer | Historical point-in-time VWAP-24H rates provide supporting FX context |
| Corridor analysis | Historical pair behavior may require separate datasets | Historical OHLC exchange-rate timeseries support longer-period analysis |
| Reconciliation | Historical FX context may be difficult to reproduce | Historical currency data can complement stored internal quote and transaction records |
| Integration | Live and historical currency workflows may rely on separate data sources | REST, WebSocket, JSON-RPC, and MCP provide access for different supported workflows |
Use the Right Interface at Each Stage
REST for Quotes and Historical Review
REST can support workflows where an application needs current VWAP-24H reference data or historical currency information on demand.
This can include quote-generation services, historical investigation, reconciliation support, and corridor analysis.
WebSocket for Live Reference-Rate Monitoring
WebSocket streams live exchange-rate updates for supported currency-data workflows.
Backend systems can monitor these updates while the provider independently determines quote validity, repricing, executable rates, liquidity, and settlement.
For historical review and reconciliation, use supported historical access rather than WebSocket.
JSON-RPC for Service Integration
JSON-RPC provides RPC-style access to supported live and historical currency data.
It can fit service architectures where currency information needs to be integrated into transfer, reporting, or analytical systems.
MCP for Structured Currency-Tool Access
MCP gives compatible applications and AI systems structured access to supported currency tools.
It can support workflows such as retrieving supported historical currency information or exploring exchange-rate data. Operational decisions, transaction handling, and compliance remain the responsibility of the remittance provider.
Keep the FX Reference Traceable Through the Transfer
A remittance workflow can separate each responsibility clearly:
ReferenceRetrieve the current VWAP-24H reference exchange rate.
PriceDetermine the provider's customer-facing rate, spread, fees, rounding, and other pricing rules.
QuotePresent send and receive amounts, fees, and validity according to the provider's policy.
MonitorObserve live reference-rate updates where required.
ExecuteSource liquidity and process conversion, funding, settlement, and payout through the provider's own financial infrastructure.
RecordPreserve the actual customer quote, pricing inputs, timestamps, transaction details, and other required internal records.
ReconcileUse those internal records as the source of truth for the transaction, with FinFeedAPI historical currency data providing additional market context where useful.
The separation is deliberate: FinFeedAPI tells the system what its supported reference currency data showed. The remittance provider determines what was offered, executed, settled, and paid out.
Build Remittance FX Workflows on Consistent Reference Data
Use current VWAP-24H reference exchange rates as inputs for supported transfer corridors, live exchange-rate updates for monitoring, and historical point-in-time rates and OHLC timeseries for reconciliation support, corridor analysis, and historical investigation.
FinFeedAPI Currencies API gives remittance teams a structured reference currency-data layer while leaving executable pricing, liquidity, rate locking, payments, settlement, and payout under the provider's control.
Remittance providers also remain responsible for applicable licensing, KYC, AML, sanctions screening, consumer disclosures, data retention, and other legal and regulatory compliance requirements. FinFeedAPI does not provide these compliance workflows.