Skip to main content

Manage Customer Accounts

To process payments through Inventi, accounts need to be registered in the platform. You have two options:

Use Existing IBANs

Forward your existing customer IBANs to the platform for payment processing

Generate New IBANs

Create new accounts with Inventi-generated IBANs connected to CSM
In this section, you’ll learn how to:
  • Register accounts (existing or new) in the platform
  • Support both private individuals and business entities
  • Manage account lifecycle (open, close, update)

Account Types

Private Accounts

Individual customer accounts with personal holder identity

Legal Accounts

Business accounts requiring organization identification

API Reference

Search Accounts

Find accounts with cursor pagination

Create Account

Create a new customer account

Get Account

Retrieve account details by ID

Update Account

Modify account information

Change Status

Open or close an account

Business Requirements

Every POST /accounts request must include an Idempotency-Key header to prevent duplicate accounts during retries.Implementation:
  • Generate a UUID per account creation intent
  • Persist the key until creation is confirmed
  • Retry with the same key if timeout occurs
Without idempotency, network retries can create duplicate accounts.
Your clientAccountId links platform accounts to your internal records and must be unique across your system.Store this mapping:
Enforce a uniqueness constraint in your database before calling the API.
Account type cannot be changed after creation.
Never change account status through the update endpoint.
Using the wrong endpoint may result in validation errors.
The accounts endpoint uses cursor-based pagination for consistent results.Rules:
  • limit: 1-100 (default 20)
  • Use meta.nextPageToken to page forward
  • Use meta.previousPageToken to page backward
  • Treat tokens as opaque (do not parse)
For sync jobs, loop with nextPageToken until empty and store the last token for checkpointing.
Log these events for compliance:
  • Account registration (clientAccountId, platform ID, IBAN)
  • Status changes (who, when, old → new)
  • Update operations (before → after values)
  • API failures and response codes

Account Lifecycle

Register an Account

Use this endpoint to register a new account in the platform. If you provide bank details (countryCode, bankCode, accountCode), Inventi generates a new IBAN. Alternatively, you can register existing IBANs by providing them directly.
If you already have IBANs issued by your institution, you can register them in Inventi without generating new ones.

Request Fields

string
required
PRIVATE or LEGAL
string
required
Full name of account holder
string
Your unique identifier for this account (optional per the Create Account API reference, which says “You can optionally provide a unique clientAccountId” - this page wrongly listed it as required; move it to the Optional tab after review)
string
required
ISO country code (e.g., LT)
string
required
Bank identifier code
string
required
Account number suffix

Response Codes

Account Operations

Retrieve account details by platform ID.

Search Accounts

Use cursor-based pagination to search and list accounts.

Filter Parameters

Pagination Flow

UI pattern: Use nextPageToken for “Load more” buttons.Sync pattern: Loop until nextPageToken is null, store last successful token for resume.

Data Model

Store these fields for each account:
string
required
Platform account ID (primary key)
string
required
Your internal reference (unique)
string
required
Generated IBAN for the account
string
required
OPEN or CLOSED
string
required
PRIVATE or LEGAL
string
required
Account holder’s name
array
required
Status changes and updates with timestamps

Integration Checklist

1

Implement idempotent creation

Generate and persist Idempotency-Key for each account creation intent
2

Enforce unique clientAccountId

Add database constraint before calling the API
3

Store account mappings

Persist clientAccountIdidiban relationships
4

Separate data and status updates

Use PATCH for data, /status endpoint for open/close
5

Implement cursor pagination

Handle nextPageToken and previousPageToken for account listing
6

Add audit logging

Log all create, update, and status change operations

What’s Next?

With accounts created, your customers are ready to send and receive payments:

Send SEPA Payments

Create your first outbound payment

Receive Payments

Handle incoming payments via webhooks

Set Up Webhooks

Get real-time payment notifications

SWIFT Payments

Send international transfers
Last modified on July 10, 2026