Skip to main content

Go Live with Confidence

Every client goes through the same onboarding sequence: you integrate and test against the TEST environment together with the Inventi team, confirm all test scenarios pass, and only then move to production. This page describes the steps and the test scenarios you will run.
Throughout onboarding, the Inventi team assists you. Reach them via your shared Slack channel or via email.

Onboarding Steps

1

Exchange access details

You share the IP addresses from which you will access the Back office portal and the API. Inventi whitelists them and shares your credentials for both.
2

Verify access

Log in to the SEPA Gateway Dashboard (via [tenantID].sandbox.fintenti.com) and create your team’s users with appropriate roles (see below). On the API side, obtain a token from the dashboard with your credentials and make a first test call - GET /getTransactionStatuses or GET /getTransactionTypes are good candidates.
3

Set up webhooks

Set up your webhooks URL and implement signature verification. Webhooks are the primary signal for everything that follows - set them up before running payment scenarios.
4

Run the test scenarios

Work through the scenario checklist below for each payment scheme you are onboarding (SCT, Instant, Direct Debit, SWIFT). Scenarios marked with support require the Inventi team to trigger the counterparty side.
5

Confirm readiness

When all scenarios pass, you confirm readiness and production onboarding is scheduled. Any issues found during testing are highlighted/submitted via Slack or email with the testing scenario described.

Dashboard User Roles

The first Dashboard user can create additional users with these roles:

Test Data

Test counterparty details (IBANs, BICs, receiver names) for your clearing connection are provided by your onboarding manager at the start of testing. They include:
  • A working counterparty account for successful payment scenarios
  • A non-existing/closed account that produces a rejection
  • An IBAN whose BIC cannot be resolved, for testing API validation errors
The TEST environment uses simulated funds. Test nostro balances can be topped up on request, and balances may behave differently than production (for example, they can go negative).

Test Scenarios

The tables below are the reference version of the test plan. Once you do these test cases and set everything up from your end - let us know in the slack channel. If you face any issues while doing these test cases, we are here to help via slack or email.

Scheme and Connection Notes

  • SCT vs Instant: the scenario list is the same for both schemes - run it once per scheme. Instant payments settle in seconds; if instant confirmation mode is enabled for your tenant, also test accepting and rejecting a Pending confirmation payment.
  • SEPA Direct Debit: if you are onboarding SDD, an additional scenario set covers collections, rejections, returns, refunds and reversals - provided during onboarding.
  • Clearing connections (CENTROlink / EKS): the API, statuses, webhooks and scenarios are identical regardless of which clearing connection your tenant uses. Test counterparty data and statement details are connection-specific and are provided with your test credentials.

What’s Next?

Authentication

Set up API credentials and tokens

Send Payments

Create your first outbound payment

Receive Payments

Handle incoming payments via webhooks

Webhooks Management

Configure and filter webhook notifications
Last modified on July 16, 2026