Versioned gateway contract
A typed /api/v1 contract handles account resolution, quotes, idempotent payment instructions, status reads, reversal requests and signed callbacks.
Engineering architecture
A payment orchestration layer with an explicit regulated boundary.
Vyloca is not presented as a bank or payment processor. It is a provider-neutral experience and orchestration system designed to integrate with licensed infrastructure through a controlled, auditable contract.
System layers
Canonical payment state machine
One explicit transition model governs delayed, credited, declined, reversal-pending and reversed states. Invalid or replayed transitions fail closed.
Durable transaction record
Atomic database functions enforce quote uniqueness, idempotency and append-only operational events. Production does not fall back to process memory.
Partner security boundary
Server-only credentials, bounded payloads, constant-time secret comparison and timestamped HMAC callbacks protect the integration surface.
Operational traceability
Every gateway response carries a request identifier. Structured, payload-free telemetry supports incident correlation without logging account or card data.
Regulated execution stays outside Vyloca
Identity decisions, card handling, FX execution, safeguarding, transfers, sanctions screening and regulatory reporting remain with licensed partners.
Core invariants
- One quote can create at most one payment.
- One idempotency key cannot identify different instructions.
- Raw card credentials never enter Vyloca.
- Only signed, fresh partner callbacks can finalize delayed outcomes.
- Terminal payment states cannot be silently rewritten.
- Production routes require durable storage and fail closed without it.
Review the interface
Technical reviewers can inspect the machine-readable contract and the live health surface without relying on marketing claims.