Changelog

What we shipped, improved, and fixed across the platform — hosted checkout, payment rails, stablecoin, issuing, and compliance. Hand-curated highlights, newest first.

Last updated: 2026-07-06

  1. Two-factor enrollment QR code

    Authenticator-app enrollment on the 2FA setup and verification screens now renders a scannable QR code.

  2. Hosted checkout dispatch hardening

    Checkout completion takes an atomic claim before dispatching to a payment provider, so a session is charged at most once even under concurrent completion attempts. Fraud-engine evaluation errors now fail closed.

  3. Multi-rail orchestration idempotency

    Idempotency claims in the orchestration engine were hardened: concurrent retries of the same payment or refund now resolve to a single provider dispatch.

  4. SEPA and ACH return handling

    SEPA returns (pacs.004) are parsed against the ISO reason-code table, ingested via a signed sponsor-bank webhook, and surfaced through reconciliation and payment-intent state. ACH returns propagate to the payout engine and reconciliation automatically.

  5. Cross-chain USDC transfer verification

    Cross-chain USDC transfers over Circle's CCTP verify burn and mint receipts on-chain, poll attestations server-side against per-chain finality windows, and support CCTP v2 fast transfers.

  6. Issuing program surfaces

    Issuer-processor authorization webhooks, a hold → capture → reversal transaction ledger, spend-limit interval resets, and an issuer-side dispute lifecycle. PAID operates as a program manager — live card issuance requires BIN-sponsor bank configuration.

  7. Stablecoin on/off-ramp legs and rate snapshots

    Fiat legs for stablecoin on/off-ramps (gated behind custody grants), an auto-settlement worker that advances mint and burn flows unattended, and FX quotes that replay deterministically from a rate snapshot.

  8. Consent-gated rail orchestration

    The responsibility-consent gate now runs on live authorization — rails without recorded consent are never offered. Every routing decision is audited with the routes considered, and consent records live in a tamper-evident hash-chained book.

  9. Wallet checkout payer screening

    The wallet-button checkout path now runs the same payer sanctions and embargoed-jurisdiction screen as the card path, closing the last gap so payer screening covers every checkout path.

  10. Data-sharing consent at onboarding

    Merchants choose how much data to share at onboarding (essential vs full). PAID can pull onboarding data from a merchant-exposed endpoint to pre-fill forms, and downgrading a tier erases captured data outside the granted scope.

  11. Compliance screening depth

    Payer and merchant sanctions screening on the hosted checkout and inline authorize paths, self-hosted PEP and adverse-media screening, AML transaction aggregation for structuring detection, and terminated-merchant (MATCH) screening at merchant go-live.

  12. Ledger and custody hardening

    The hash-chained ledger anchors signed checkpoints on a schedule for tamper evidence once an anchoring signing key is configured, and outbound money movement is governed by a central custody-policy chokepoint.

  13. Network tokenization readiness (VTS / MDES)

    Visa (VTS) and Mastercard (MDES) network-token provisioning clients are wired into the API; live provisioning activates once network credentials are configured. Without them, dev and CI fall back to an offline in-memory provisioner.

This changelog covers highlights, not every change. For the complete, current API surface, see the API reference and developer docs.