Monerium IBAN Integration

Share a user’s verified KYC data with Monerium to enable IBAN issuance

Before starting, read KYC Sharing (Sumsub Flow) as this guide builds directly on the share-token flow described there.

Gnosis Pay integrates with Monerium to offer users an IBAN linked to their account. Rather than requiring the user to complete KYC a second time with Monerium, their already-verified Sumsub identity data can be shared directly with Monerium, which reuses it to populate and verify the user’s Monerium profile.

Monerium is configured as a Sumsub recipient on our end, meaning your integration flow requests a Sumsub share token scoped specifically for Monerium’s client ID, then forwards that token to Monerium.

How it works

1. Request a Sumsub share token for Monerium

   Call POST /kyc/import-partner-applicant with forClientId set to Monerium’s Sumsub client ID.

   Sandbox

           curl --request POST \
             --url https://core.sandbox.gnosispay.in/user-api/kyc/import-partner-applicant \
             --header 'Authorization: Bearer <token>' \
             --header 'Content-Type: application/json' \
             --data '{
               "forClientId": "<monerium_sumsub_client_id>",
               "ttlInSecs": 1200
             }'
   

   Production

           curl --request POST \
             --url https://core.prod.gnosispay.com/user-api/kyc/import-partner-applicant \
             --header 'Authorization: Bearer <token>' \
             --header 'Content-Type: application/json' \
             --data '{
               "forClientId": "<monerium_sumsub_client_id>",
               "ttlInSecs": 1200
             }'
   

   The response returns a single-use token:

       {
         "token": "<string>",
         "forClientId": "<monerium_sumsub_client_id>"
       }
   

   This token is single-use and expires after ttlInSecs (default 1200 seconds). Request a fresh token immediately before passing it to Monerium, don’t generate it ahead of time and store it.

2. Share the token with Monerium

   This call is made directly to Monerium’s API using your own Monerium partner credentials (BearerAuth) not a Gnosis Pay endpoint. Note Monerium’s sandbox uses .dev (fake money) and production uses .app (real money),this differs from Gnosis Pay’s own .sandbox / .prod domain pattern, so don’t mix them up.

   Pass the token from Step 1 to Monerium’s Share KYC Data endpoint, under the personal object, with provider set to "sumsub".

   Sandbox

           curl --request POST \
             --url "https://api.monerium.dev/profiles/{profile}/share" \
             --header 'Authorization: Bearer <monerium_bearer_token>' \
             --header 'Accept: application/vnd.monerium.api-v2+json' \
             --header 'Content-Type: application/json' \
             --data '{
               "provider": "sumsub",
               "personal": {
                 "token": "<sumsub_share_token>"
               }
             }'
   

   Production

           curl --request POST \
             --url "https://api.monerium.app/profiles/{profile}/share" \
             --header 'Authorization: Bearer <monerium_bearer_token>' \
             --header 'Accept: application/vnd.monerium.api-v2+json' \
             --header 'Content-Type: application/json' \
             --data '{
               "provider": "sumsub",
               "personal": {
                 "token": "<sumsub_share_token>"
               }
             }'
   

   Monerium uses the supplied token to fetch the user’s data directly from Sumsub and populates the relevant sections of the user’s Monerium profile. Each section that receives sufficient data transitions to pending; any section that remains incomplete stays incomplete.

3. Data reaches Monerium

   Once Monerium has ingested the shared KYC data, the relevant sections of the user’s profile move to pending review on Monerium’s side. No further action is needed from your integration until Monerium’s review completes.

4. Request IBAN issuance

   Once the profile’s KYC sections are approved by Monerium, you can request IBAN issuance directly through Monerium’s own API.

   See Monerium’s own API reference for the IBAN issuance endpoint, this is a separate call from KYC sharing above.

Summary