Svea
Visma.net

Svea + Visma.net

Integration documentation and guides

Getting Started · 3

Getting Started

3

Getting Started

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

Svea

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

10 minutes
  1. 1

    Contact Svea to get started

    Start with your Svea sales or onboarding contact to set up the merchant account and test environment.

  2. 2

    Get the test credentials

    Ask Svea for the CheckoutMerchantId and CheckoutSecret for the test environment first.

  3. 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. 4

    Paste the values into Junipeer

    Enter the CheckoutMerchantId and CheckoutSecret in Junipeer.

  5. 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.

Visma.net

oauth2 · Until access is revoked, disconnected, or re-authentication is required

3 minutes
  1. 1

    Open the Visma.net connector in Junipeer

    Start the Visma.net connection from the relevant connector or onboarding step in Junipeer.

  2. 2

    Click Connect

    Use the connect action in Junipeer to start the Visma Connect sign-in flow.

  3. 3

    Sign in with the correct Visma account

    Choose the Visma account that has access to the Visma.net environment and company that should be connected.

  4. 4

    Approve the requested access

    Review the OAuth consent screen in Visma Connect and approve the connection if the account and environment are correct.

  5. 5

    Return to Junipeer and verify the connection

    After the approval flow completes, go back to Junipeer and make sure the Visma.net connector shows as connected.