Rextie API integration services (USD/PEN OpenFinance)

Deliverables checklist

• API specification in OpenAPI 3.1 (Swagger) format
• Protocol report covering the auth handshake, token lifetime, request signing and 2FA challenge flow
• Runnable source code (Python and Node.js) for login, rate retrieval, operation creation and statement export
• Postman collection with sandbox and production profiles
• Automated tests, replay traces and a sample BI dashboard fed by the statement endpoint
• Compliance dossier covering Peru's Personal Data Protection Law (29733), SBS expectations and ISO 27001 control mapping

Feature modules at a glance

• Login & KYC mirror — DNI/RUC validation, OAuth-like session, refresh and revocation; used to back call-center and treasury dashboards.
• Operation creation — Quote-lock, amount, source bank, destination bank, voucher upload; used for STP order routing from an ERP.
• Statement & export — Paginated history with status filter; used for monthly reconciliation, audit and tax reporting.
• Rate intelligence — Buy/sell mid, spread vs. interbank, historical series; used to build pricing and hedging dashboards.
• SME & corporate APIs — Multi-user roles, approval thresholds and CitiFX Pulse-backed quotes for corporates.
• Notifications & widgets — Watch and widget feeds parity, push events on funding and settlement.

1. SME treasury reconciliation

A Lima-based importer settles supplier invoices weekly. Their ERP triggers a Rextie operation through our API, locks the quote, transfers PEN from BCP and receives USD on Interbank. The statement endpoint feeds back into the ERP each night so accounting can match the operation ID to the supplier invoice. This maps to the OpenFinance "payment initiation + transaction history" pattern.

2. Real-time FX dashboard

A Peruvian e-commerce holding aggregates Rextie's published bid/ask alongside BCR reference rates and BCP/BBVA spot quotes to drive a hedging dashboard. The rate feed is polled or subscribed to, normalised into a single time-series schema and exposed as an internal API. This is a classic OpenData angle — the data is public-facing but consumed at scale.

3. Compliance and audit pipeline

An external auditor needs every USD/PEN exchange of a regulated client over the last 24 months, including counter-bank, applied rate and voucher. Our statement export returns paged JSON plus signed PDFs, with consent records that satisfy the new Supreme Decree No. 016-2024-JUS data-breach and DPO obligations.

4. Corporate multi-user portal

A corporate treasury team has three approvers and one initiator. Our integration mirrors Rextie's enterprise role flow: an analyst creates the operation, a CFO approves above a threshold, and CitiFX Pulse-backed pricing is honoured. All steps emit webhooks so the company's internal portal can show status without polling.

5. Payouts & freelance disbursement

A platform that pays Peruvian freelancers in USD uses Rextie as the off-ramp: invoices are batched, exchanged into PEN at a locked quote, and disbursed to each freelancer's bank. Our integration covers batch creation, settlement webhooks and per-recipient receipts so the platform can post each payment back to its ledger.

1. Authorization & session

POST /api/v1/rextie/auth/login
Content-Type: application/json

{
  "document_type": "DNI",
  "document_number": "********",
  "password": "********",
  "device_fingerprint": "ua:android-13;app:6.x"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rfk_...",
  "expires_in": 3600,
  "user": { "id": "usr_8821", "type": "business", "ruc": "20*********" }
}

2. Statement / operation history

GET /api/v1/rextie/operations?from=2026-04-01&to=2026-04-30&page=1
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "page": 1, "page_size": 50, "total": 137,
  "items": [
    {
      "operation_id": "OP-7F92A1",
      "created_at": "2026-04-12T14:08:55-05:00",
      "side": "USD_TO_PEN",
      "amount_usd": 12500.00,
      "rate": 3.7184,
      "amount_pen": 46480.00,
      "fee_pen": 0.00,
      "from_bank": "BCP", "to_bank": "INTERBANK",
      "status": "SETTLED",
      "voucher_url": "https://.../OP-7F92A1.pdf"
    }
  ]
}

3. Webhook: settlement event

POST https://your-app.example/webhooks/rextie
X-Rextie-Signature: t=1746230400,v1=8a4e...
Content-Type: application/json

{
  "event": "operation.settled",
  "operation_id": "OP-7F92A1",
  "status": "SETTLED",
  "settled_at": "2026-04-12T14:32:11-05:00",
  "rate": 3.7184,
  "destination_bank": "INTERBANK"
}

# verify HMAC-SHA256 of the raw body using the shared secret
# reject if older than 5 minutes or signature mismatches

Regulatory framing

Rextie is registered with the Superintendencia de Banca, Seguros y AFP (SBS) as a money exchange operator and is the only Peruvian fintech in the segment with ISO 27001 certification. Integrations must respect Peru's Personal Data Protection Law No. 29733 and the new regulation under Supreme Decree No. 016-2024-JUS, in force since 30 March 2025, which mandates a Data Protection Officer and breach notification to the APDP. Reference: Personal Data Protection Law overview.

Operating principles

• Customer-authorized access only — no bypass of 2FA or device binding.
• Data minimization: integrations request the minimum fields needed for the use case.
• Consent records and access logs retained for auditability.
• ISO 27001-style control mapping on the adapter, mirrored from Rextie's own posture.
• Tokens stored encrypted at rest; revocation hooks tied to customer offboarding.

About OpenFinance Lab

We are an independent studio focused on fintech and OpenData API integration. Our team includes engineers from banks, payment gateways, protocol research and cloud platforms. We know the SBS, BCRP and APDP expectations as well as multi-region privacy rules, and we ship end-to-end financial APIs under security and compliance constraints.

• Payments, digital banking, FX and cross-border clearing
• Enterprise API gateways and security reviews
• Custom Python / Node.js / Go SDKs and test harnesses
• Full pipeline: protocol analysis → build → validation → compliance
• Source code delivery from $300 — runnable API source plus docs, paid after delivery upon satisfaction
• Pay-per-call API billing — access our hosted endpoints and pay only per call, no upfront cost

Contact

Send us your target app, the data you want to consume and your timeline. We respond within one business day.

Contact page

Engagement workflow

1. Scope confirmation: which Rextie surfaces (login, operations, rates, webhooks) you actually need.
2. Protocol analysis and API design (2–5 business days).
3. Build and internal validation against a sandbox account (3–8 business days).
4. Documentation, OpenAPI spec and Postman collection (1–2 business days).
5. Hand-off and one round of post-delivery support; typical first delivery is 5–15 business days.

FAQ

Does Rextie publish a public developer API?

Which Rextie data can be integrated into my stack?

How long does a Rextie integration take?

How do you keep the integration compliant in Peru?