Integrations

Supported integrations

The inbound payment sources Valverna can ingest from. Render this in your onboarding so you only ask users for processors you can actually pull data from — instead of signing up a merchant whose processor isn't supported yet. Valverna owns these ingest integrations; you build on top and read the normalized transactions.

List integrations

GET /v1/integrations

Authenticated like every /v1 route, but free: it is not metered and never draws down your prepaid balance, so you can call it before onboarding a single user. No scopes required.

Response fields

platform optional

Stable lowercase id, e.g. stripe — matches source.platform on transactions.

status optional

live — Valverna ingests it automatically via a native adapter. partner — no native adapter yet, but it flows in when an approved ingestion partner pushes it through the write API. planned — on the roadmap, not yet reachable.

method optional

How data flows in: webhook (a Valverna-built adapter) or partner_api (pushed to POST /v1/transactions).

category optional

payments, pos, or ecommerce.

country optional

Optional ISO-2 when the source is region-specific (e.g. SE for Swish).

Response 200

{
  "data": [
    {
      "platform": "stripe",
      "name": "Stripe",
      "category": "payments",
      "status": "live",
      "method": "webhook"
    },
    {
      "platform": "swish",
      "name": "Swish",
      "category": "payments",
      "status": "partner",
      "method": "partner_api",
      "country": "SE"
    }
  ]
}