Svea + Visma Spiris

Integration documentation and guides

Getting Started · 2

Getting Started

Start with credentials, setup steps, and the key guides for this pair.

token · The merchant credentials stay valid until changed or revoked. Authentication tokens are generated from these credentials per request.

10 minutes

1
Contact Svea to get started
Start with your Svea sales or onboarding contact to set up the merchant account and test environment.
2
Get the test credentials
Ask Svea for the CheckoutMerchantId and CheckoutSecret for the test environment first.
3
Store the values securely
Save both the merchant ID and the secret securely because they are both required to build the authentication token.
4
Paste the values into Junipeer
Enter the CheckoutMerchantId and CheckoutSecret in Junipeer.
5
Repeat for live when you are ready
Before go-live, request and use the live credentials for the production environment if they differ from the test setup.

token · Varies by agreed setup

Varies by project

1
Confirm the exact product and environment
Verify the product variant, environment, tenant, and any middleware involved before configuring credentials.
2
Let Junipeer confirm the auth pattern
Use the agreed Junipeer implementation scope to confirm whether the setup uses API keys, service users, OAuth, tokens, or another method.
3
Create or receive the technical credentials
Have the system owner, vendor, or implementation partner create the required integration access according to the agreed setup.
4
Add the credentials in Junipeer
Enter the issued credentials, host details, and any tenant-specific identifiers in the Junipeer admin when requested.
5
Verify in a non-production environment first
Run a controlled connection test before enabling a live data flow.