Exchange Rate Data Methodology & Standards

1. Source Hierarchy & Aggregation

EnParaleloVzla distinguishes strictly between official central banking references and non-governmental free-market indicators. Our architecture ingests rate data through two distinct channels:

• Official BCV Benchmark: Extracted directly from the Central Bank of Venezuela’s published daily closing averages. This value represents the legal, volume-weighted result of interbank operations conducted by authorized financial institutions.
• Parallel Indicator (EnParaleloVzla): Surveyed from prominent digital exchange platforms, peer-to-peer (P2P) trading volume, and OTC desks. Outlier values that deviate significantly from median trading bands are filtered out to prevent artificial spikes.

2. Data Validation & Anti-SSRF Security

Every incoming data payload passes through multi-layer verification before display or storage:

• HTTP status codes must evaluate to 200 OK with strict Content-Type: application/json headers.
• Exchange rate values must be finite, strictly positive floating-point numbers within plausible historical bounds.
• External API requests are validated against SSRF protection policies preventing loopback (127.0.0.1) or RFC1918 intranet lookups.
• All data is sanitized upon ingestion and escaped upon presentation using WordPress VIP standards.

3. Caching & Freshness Status Policy

To maintain exceptional Core Web Vitals and protect upstream data servers, rates are cached server-side using the WordPress Transients API with a default 15-minute lifecycle. Data freshness is categorized into four distinct statuses:

4. Timestamp Standards

All exchange rate retrieval and update events are recorded internally in UTC (Coordinated Universal Time) Unix timestamps. When presented on the website, timestamps are dynamically formatted according to WordPress timezone settings, ensuring exact clarity regardless of visitor location.