Question 1

What is the actual cost reduction compared to SWIFT?

Accepted Answer

Our clients report an average 78% reduction in total international settlement cost. While SWIFT charges $25-50 per transaction plus 1-3% FX spreads, Infracash operates with fixed fees starting at 0.1% and FX spread below 0.3%. For volumes above $1M/month, TCO drops further with tiered pricing.

Question 2

How does automatic reconciliation work?

Accepted Answer

Each transaction generates an atomic cryptographic proof linking the payment order, on-chain execution, and final settlement. This eliminates the need for manual D+2/D+3 reconciliation typical of SWIFT. Your ERP receives real-time webhooks with status for each step, enabling same-day accounting close.

Question 3

What is the typical ROI and timeline?

Accepted Answer

Average ROI is 340% in the first year, with payback in 3-4 months. This considers: (1) direct savings on settlement fees, (2) elimination of manual reconciliation costs, (3) working capital release from 2-5 day float, and (4) reduced FX exposure with sub-60s settlement. For companies with volume above $5M/month, payback can be under 60 days.

Question 4

How does Infracash impact working capital?

Accepted Answer

With final settlement in under 60 seconds (vs. 2-5 days on SWIFT), capital trapped in transit is released immediately. For a company processing $10M/month, this can represent $500K-1.5M of additional working capital permanently available. Additionally, cost predictability (fixed fees) facilitates cash flow planning.

Question 5

Is there FX risk in the operation?

Accepted Answer

FX risk is minimized by settlement speed. Since conversion and settlement occur in under 60 seconds, FX exposure is virtually eliminated. Compared to SWIFT, where the 2-5 day float exposes operations to exchange rate variations, Infracash offers total predictability. We also offer rate lock at order time for scheduled operations.

Question 6

What is the platform's technical architecture?

Accepted Answer

Infracash operates as a decision layer between bank and digital rails. The architecture comprises: (1) RESTful API Gateway with OAuth 2.0 + API Keys authentication, (2) Decision Engine evaluating compliance, cost, and speed in real time, (3) Rail Connectors for PIX, SWIFT, SEPA, ACH, FPS, and blockchains, (4) MPC Custody via Dfns for secure custody, and (5) Observability Layer with logs, metrics, and alerts. Everything runs on AWS infrastructure with multi-AZ redundancy.

Question 7

How long does API integration take?

Accepted Answer

Basic integration (sending and receiving payments) can be completed in 2-4 hours with our SDK. The process: (1) obtain API Keys in sandbox, (2) install SDK (Node.js, Python, Java, Go), (3) configure webhooks for status updates, and (4) test in sandbox environment with simulated real data. For enterprise ERP integrations (SAP, Oracle, Totvs), we offer pre-built connectors reducing time to 1-2 weeks.

Question 8

How does observability and monitoring work?

Accepted Answer

The platform offers complete observability across three layers: (1) Transaction Tracing — each transaction has a unique trace ID tracking from API call to final settlement through compliance check, rail selection, and settlement; (2) Real-time Dashboard — latency, throughput, success rate, and volume metrics per rail, accessible via API or UI; (3) Alerting — configurable webhooks for anomalies, failures, and SLA breaches. Everything integrates with Datadog, Grafana, or any observability stack via OpenTelemetry.

Question 9

What is the availability SLA and how is it guaranteed?

Accepted Answer

The contractual SLA is 99.97% uptime, guaranteed by: (1) multi-AZ architecture on AWS with automatic failover, (2) per-rail circuit breakers isolating failures without affecting other rails, (3) health checks every 30 seconds with auto-healing, and (4) SLA credits in case of violation. The last 12 months show 99.99% effective availability.

Question 10

Does the platform support white-label and multi-tenant?

Accepted Answer

Yes. The architecture is natively multi-tenant with complete data isolation, configurations, and limits per tenant. White-label mode allows fintechs and banks to offer Infracash infrastructure under their own brand, with: (1) customizable branding (logo, colors, domain), (2) APIs under own domain, (3) personalized dashboards, and (4) independent configuration of rails, limits, and compliance rules per tenant.

Question 11

How does compliance-before-execution work?

Accepted Answer

Every transaction undergoes compliance verification BEFORE execution. The flow: (1) API receives payment order, (2) Decision Engine runs KYC/KYB checks, sanctions screening (OFAC, EU, UN), PEP check, and AML rules in real time, (3) if approved, transaction is routed to the most efficient rail, (4) if rejected, the reason is logged with complete audit trail. No transaction touches a settlement rail without prior compliance engine approval.

Question 12

Which regulatory frameworks does Infracash comply with?

Accepted Answer

Infracash operates in compliance with: (1) BACEN — Resolution 277/2022 and FX regulations, (2) MiCA — Markets in Crypto-Assets Regulation (EU), (3) GENIUS Act — Guiding and Establishing National Innovation for U.S. Stablecoins, (4) LGPD/GDPR — personal data protection, (5) FATF/GAFI — anti-money laundering recommendations. We also maintain SOC 2 Type II certification and ISO 27001 in progress.

Question 13

How is the audit trail generated?

Accepted Answer

Each transaction generates an immutable record with: (1) timestamp for each step (receipt, compliance check, rail selection, execution, settlement), (2) result of each compliance check (approved/rejected + reason), (3) cryptographic hash of on-chain transaction, (4) operator identity and source IP, (5) version of compliance rules applied. All records are stored with 7-year retention and can be exported in audit-compatible format (CSV, JSON, PDF).

Question 14

Does Infracash support real-time sanctions screening?

Accepted Answer

Yes. Screening runs in real time against daily-updated lists: OFAC SDN (US), EU Consolidated List, UN Security Council, COAF (Brazil), and PEP lists from 200+ jurisdictions. Verification occurs in under 200ms and is a mandatory part of the compliance-before-execution flow. In case of partial match, the transaction is paused for manual review with 4-hour SLA. Partnership with Chainalysis for on-chain analysis.

Question 15

How does Infracash handle Travel Rule requirements?

Accepted Answer

Infracash implements Travel Rule (FATF Recommendation 16) natively for all transactions above regulatory thresholds. Originator and beneficiary information is securely transmitted between VASPs using standardized protocols. For cross-border transactions, data is automatically formatted per destination jurisdiction requirements (BACEN, FinCEN, FCA, etc.).

Question 16

What differentiates Infracash from other payment providers?

Accepted Answer

Infracash is not a payment provider — it's a programmable settlement infrastructure layer. The fundamental difference: (1) Rail unification — a single API connects PIX, SWIFT, SEPA, ACH, FPS, and blockchains, eliminating the need for multiple vendors; (2) Decision Engine — intelligent routing choosing the most efficient rail in real time considering cost, speed, and compliance; (3) Compliance-before-execution — regulatory verification before execution, not after; (4) White-label ready — your company can offer the infrastructure under its own brand.

Question 17

What is the addressable market and strategic opportunity?

Accepted Answer

The cross-border payments market moves $150 trillion/year (McKinsey 2024), with average fees of 1.5-3% and 2-5 day latency. Financial asset tokenization is expected to reach $16 trillion by 2030 (BCG). Infracash positions at the intersection of these two markets: programmable settlement connecting traditional banking to the digital economy.

Question 18

Who are typical Infracash clients?

Accepted Answer

Our clients are institutions processing significant international payment volumes: (1) Banks and financial institutions modernizing settlement infrastructure, (2) Fintechs needing multi-currency rails to scale globally, (3) Companies with international operations (import/export, global payroll, treasury), (4) Exchanges and digital asset platforms needing institutional on/off-ramp, (5) Marketplaces with international sellers. Recommended minimum volume is $100K/month.

Question 19

What is the product roadmap for the next 12 months?

Accepted Answer

The roadmap includes: Q2 2026 — Rail expansion to Asia-Pacific (RTGS India, FPS Singapore) and Programmable Reserve Management module launch; Q3 2026 — Digital Currency Issuance platform for institutional tokenized asset issuance with on-chain governance; Q4 2026 — Mobile SDK for native app integration and white-label program expansion for Tier 2 banks.

Question 20

How does Infracash integrate with my TMS/ERP?

Accepted Answer

We offer pre-built connectors for SAP Treasury, Oracle Cash Management, Totvs Protheus, and Kyriba. Integration is via REST API + webhooks, enabling: (1) payment order submission directly from TMS, (2) automatic settlement confirmation receipt, (3) real-time cash position updates, and (4) automatic reconciliation with reference matching. For unlisted TMS, the RESTful API allows custom integration in 1-2 weeks.

Question 21

How does multi-currency liquidity management work?

Accepted Answer

The platform offers: (1) Unified liquidity pool — consolidated view of balances in BRL, USD, EUR, GBP, and stablecoins, (2) Automatic conversion — Decision Engine converts automatically on the most efficient rail, (3) Netting — automatic offsetting of opposing flows to reduce conversion volume, (4) Programmatic reserves — automatic reserve allocation in stablecoins with programmable yield, and (5) Position alerts — configurable notifications for balance limits per currency.

Question 22

What is the treasury onboarding process?

Accepted Answer

Treasury onboarding follows 4 steps: (1) Discovery Call — understanding your flows, volumes, currencies, and current systems (30 min); (2) Configuration — account setup, limits, enabled rails, and compliance rules (1-2 business days); (3) Integration — TMS/ERP connection via API or pre-built connectors (1-2 weeks); (4) Go-live — assisted operation period with dedicated support (2 weeks). The complete process takes 3-4 weeks from first contact to go-live.

Question 23

How does FX hedging work on the platform?

Accepted Answer

The platform offers two modes: (1) Spot with lock — at order time, the rate is locked for 30 seconds, guaranteeing execution at quoted price; (2) Programmable forward — for recurring operations (payroll, suppliers), future conversions can be scheduled with pre-agreed rates. Sub-60s settlement eliminates slippage risk that exists in 2-5 day SWIFT operations.

Frequently Asked Questions

We use cookies