Intergiro developer portal

# Introduction

Individuals represent end users and it's important to have them properly registered before they can use accounts or cards. This process is called onboarding.

IMPORTANT

Pending actions feature is mandatory for Cards / Onboarding as a Service API implementation. This part is integral, as specific API functionalities and operational processes are dependent on the successful integration of the Pending Actions feature. For in-depth insights and integration guidelines, refer to our Pending Actions (opens new window) article.

# Create individual

The first step is to provide some basic personal information about an individual.

Example create individual request:

 



















POST /v3/individuals

Content-Type: application/json
Authorization: Bearer <access_token>

{
  "first_name": "John",
  "last_name": "de Mayor",
  "email": "m6dreey@goes.es",
  "phone_number": "46627211111",
  "date_of_birth": "1991-12-06",
  "address": {
  	"country_code": "SE",
  	"street1": "Mälarö torg 2",
  	"city": "Ekerö",
  	"region": "Ekerö",
  	"postal_code": "178 30"
  }
}

Address is optional.

Once created, you can query an individual by calling GET /v3/individuals/:id.

# Initiate onboarding

Onboarding process involves redirecting the end user to an URL, where we collect all necessary information required to open an account.

# Obtaining onboarding form URL

First you'll need to initiate individual onboarding to get the redirect_url:

 






 

POST /v3/individuals/9c017aec-c952-4713-aa10-11708cb0d11a/onboard

Content-Type: application/json
Authorization: Bearer <access_token>

{
  "return_url": "https://example.com/onboarding_callback"
}

Response:

 


 



HTTP 200 OK

{
  "redirect_url": "https://integrate.intergiro.com/onboarding/...",
  "expires_at": "2021-02-08T14:09:15.000Z"
}

# Sending the user to the Onboarding flow

Now you'll need to open the browser and send the user to the redirect_url provided earlier.

REQUIREMENT

To ensure the best user experience (UX), along with stable operation of the onboarding flow and biometric functions, we require the following:

  1. Native Applications:
  1. Web Applications:
  • Use a standalone browser for redirect experiences.
  • Customer Support Note: While we recommend using a standalone browser, it is not possible to control the browser users choose to open the app. As not all browsers are supported by our * providers in case of a user support request, please ensure the browser the user is using is supported (opens new window) by one of our providers.

Please note that we do not guarantee support for redirect flows integrated into your application in any manner other than those mentioned above.

Once initiated, wait for IndividualOnboardingDataProvided webhook event that will be delivered as soon as the user successfully completes the form. That will mean the ball is on Intergiro side as we'll be receiving the data for approval.

← Onboarding events →