V5 keeps the same resources as V4, split into focused Swagger sections.
Create a V5 credential with the scopes you need, then request a bearer
token with a comma-separated Scopes string.
{"Username":"...","Password":"...","Scopes":"online-payments, chat-api"}
· Endpoint: POST /api/v5/auth/token
· Missing scope on a call returns 401.
Getting started guide Sandbox test cards
Payments (incl. Checkout SDK), Odoo provider, PIS, stores, subscriptions, and transactions.
Hosted wallet access, tokenized cards, and instant transfers between RoxPay wallets.
POS terminals, receipts, stores, and transactions. Partners also order POS hardware from RoxPay's catalog for a portfolio merchant and pay it from their own wallet balance.
AIS, banking services, IBAN checks, and VoP.
Information lookups, contacts, contact companies, transactions, users, webhooks, and authorized domains.
WhatsApp chat iframe, notifications, and WhatsApp.
Italian e-invoices (fatture) and fiscal receipts (corrispettivi). Start with Fiscal Configuration to switch on the channels you need.
SecureSign digital contracts: create, update, list, and read. The Utilities contact book (`/api/v5/clients`) is republished here so a contracts integration can manage its contacts without a second credential — note that a contract's `ClientId` is a SecureSign recipient id from GET /api/v5/contracts/clients, not a contact `CLT-…` id.
Register and manage `.eu` domains. First-time setup: create your registrant (the legal owner) with POST /domains/registrant. Then the usual flow is list packages → check availability → quote → buy/transfer (buy/transfer charge a card for the up-front deposit). Also: list your domains, issue/revoke a domain's transfer auth-code, and toggle auto-renew (off lets a domain lapse at expiry — there is no delete endpoint).
Companies and onboarding. Restricted to Admin or Partner companies (401 otherwise).