Integration Flow

This guide walks through the technical integration flow for implementing card onboarding in your application.

​

High-Level Process

The card onboarding integration follows a webhook-driven asynchronous pattern, allowing your system to react to state changes in real-time:

​

Integration Steps

​

Step 1: Initiate Application

Your customer submits their card application through your interface. Collect all required information and submit to Nordiska’s Card Service.

​

Step 2: Submit to Card Service

Make a POST request to /api/v4/engagements/card/onboarding with the applicant’s information. The service immediately returns an onboarding ID and begins processing. The unified API supports both consumer and business onboarding through the onboardingType discriminator field:

• Set onboardingType to "CONSUMER" for consumer customers
• Set onboardingType to "BUSINESS" for business customers (requires additional company information)

​

Step 3: Handle Processing

The Card Service performs automated checks:

• KYC verification against PEP and sanctions lists
• Credit scoring through bureau integrations (Schufa, Creditsafe for businesses)
• Internal risk assessment
• For businesses: Additional KYB verification and signatory authorization checks

This typically completes within 3-10 seconds.

​

Step 3a: Document Upload (if required)

For certain business types, additional documentation may be required. When the status changes to AWAITING_DOCUMENTS:

1. Notify the customer that documents are needed
2. Collect the required documents (e.g., tax registration)
3. Upload via POST /api/engagements/card/onboarding/{onboarding-id}/documents
4. Status changes to AWAITING_DOCUMENT_REVIEW
5. Wait for document review completion

Document Upload Requirements:

• Content types: application/pdf, image/*
• Maximum file size: 10 MB
• Document types: TAX_REGISTRATION

​

Step 4: React to Webhooks

Based on the processing outcome, you’ll receive one of several webhooks:

• SIGNING_SESSION_CREATED: Application approved, redirect customer to sign
• ONBOARDING_REJECTED: Application declined, show appropriate message
• ONBOARDING_FAILED: Technical issue occurred, handle error gracefully

​

Step 5: Document Signing

For approved applications, redirect the customer to the provided signing URL. The signing service handles:

• Document presentation
• Identity verification
• Qualified electronic signature capture

​

Step 6: Card Creation

After successful signing, create the card in Enfuce:

1. Create customer record
2. Create account linked to credit facility
3. Order physical/virtual card

​

Step 7: Complete Onboarding

Once Enfuce confirms card creation, the onboarding completes and the customer can start using their card.

​

State Management

​

State Transitions

The onboarding process moves through defined states, each representing a specific phase:

​

Webhook Implementation

The integration relies on webhooks to notify your system of status changes in real-time. When key events occur (approval, signing completion, etc.), Nordiska sends HTTP POST requests to your configured webhook endpoint. Key webhook events:

• SIGNING_SESSION_CREATED: Application approved, customer needs to sign
• SIGNING_SESSION_COMPLETED: Customer finished signing documents
• ONBOARDING_COMPLETED: Entire process completed successfully
• ONBOARDING_REJECTED: Application declined during assessment
• ONBOARDING_FAILED: Technical error occurred

---

For detailed API documentation and endpoint specifications, please contact your Nordiska integration specialist.