Skip to main content
The dashboard at dashboard.caratuva.com is your operating cockpit. It is organized around the day-to-day work of getting paid: onboarding, invoicing, approvals, payouts, and reconciliation. The sidebar has: Invoices, Payout, Notifications, Developers, Enable production, and — for ops users — Admin.

​
Sign-in

Sign in with your work email — we send a magic-link (it expires in 15 minutes), no password to manage. Sessions last 12 hours. Sign out from the button in the dashboard header. The first user in an organization is an admin. The role model is admin (full access — API keys, payouts, invoices), treasurer (create and approve invoices, manage the payout destination), viewer (read-only), and ops (operational tooling, including the Admin screen). Inviting teammates and assigning roles isn’t yet self-service in the dashboard — contact support if you need more users on your organization.

​
Mode switcher

Every screen carries a mode indicator at the top. Test mode runs the full flow against a sandbox payment instance — KYB and buyer KYC auto-approve and no real money moves. Live mode operates on real rails; it unlocks once Caratuva approves your Production Access Request (see Enable production), after which you complete live KYB. Switching modes is a single click. New accounts start in test. We strongly recommend running your first end-to-end flow in test mode before going live. See Test & live modes for what each mode covers.

​
Invoices

The invoices area is where most of the work happens.

​
List

/invoices lists every invoice for your organization. Click any row to open the invoice detail, or use the per-row Duplicate action to start a repeat order.

​
Detail

The detail page shows the invoice header, the buyer, the line items, and a timeline that updates live as the payment moves through the lifecycle: 
draft → awaiting_approval → approved
      → awaiting_buyer
      → buyer_kyc_pending → buyer_kyc_approved
      → fx_quoted
      → on_ramp_pending → fiat_received
      → offramp_pending
      → settled
settled is the terminal success state. The other terminal states — expired, cancelled, and buyer_kyc_rejected — are surfaced with the reason. on_ramp_failed and offramp_failed are in-flight failures that can be retried. From the detail page you can, depending on the invoice’s state:
  • Edit the invoice (while it’s in draft or awaiting_approval).
  • Approve the invoice (a teammate other than the creator, when approval is required).
  • Invite the buyer, or resend the invitation email if the original is lost.
  • Copy the public payment link to share through your own channel.
  • Reassign the buyer (useful when a KYC flow is stuck — the new buyer starts with a clean state).
  • Cancel the invoice (only valid before the buyer funds the on-ramp).
  • Duplicate the invoice for a repeat order.

​
New invoice

/invoices/new is a step-by-step form for creating an invoice. You can also clone an existing invoice with ?from=<invoiceId> to pre-fill the buyer and line items — useful for repeat orders. See Invoicing for the full workflow including approvals and cancellation rules.

​
Payout

/payout (sidebar: Payout) runs the whole payout setup as a single flow:
  1. Accept our settlement partner’s terms of service — a one-time redirect to the partner’s hosted page and back.
  2. Verify your business (KYB) — your submission, current status, and anything we still need. See Onboarding.
  3. Register your PIX key — a single PIX key on the Brazilian bank account that receives every settlement (our settlement partner auto-detects the key type). It must match the legally verified entity. See Payouts.

​
Developers

/developers houses the integration surface for your engineering team.
  • API keys (/developers/api-keys) — issue and revoke server-to-server credentials. The plaintext secret appears exactly once at creation; copy it into your secret manager immediately.
  • Webhooks (/developers/webhooks) — register URLs that should receive lifecycle events, view recent delivery attempts, and rotate signing secrets.
Both screens are documented in detail in the API Reference.

​
Enable production (go live)

/go-live (sidebar: Enable production) is the self-service production-access request. Submit your legal name, CNPJ, business contact email, expected monthly volume, and corridors. Once Caratuva approves it, the Live option unlocks in the mode switcher; you then switch to Live and complete live KYB on the Payout page. See Test & live modes.

​
Notifications

/notifications (sidebar: Notifications) is a read-only delivery log — every message this organization has dispatched, with its channel, template, recipient, status, and reference. Filter by channel, status, and date range. Useful for verifying that buyer invitations actually went out, and for answering “did the customer receive the link?” The bell in the header is a separate, per-user inbox (powered by Courier) showing your unread alerts. There are no per-user notification preference settings today.

​
Admin (ops only)

Users with the ops role get an Admin sidebar item (/admin/production-access) for reviewing and approving organizations’ production-access requests. It isn’t visible to other roles.

​
Reports

Transfer-pricing summaries (JSON, CSV, PDF) are available via the API (GET /v1/reports/transfer-pricing), not yet as a dashboard screen. Ask our team if you need a specific breakdown for your quarterly accounting close.

​
Where to next

  • Onboarding — complete the KYB checklist.
  • Invoicing — invoice lifecycle and approvals.
  • Payouts — register your PIX destination.
  • Notifications — the delivery log and the in-product inbox.