CentralPay Documentation CentralPay Documentation
  • General information
  • Documentation
  • Developers
  • English
    • FrenchSwitch to French
CentralPay Documentation CentralPay Documentation
  • General information
  • Documentation
  • Developers
  • English
    • FrenchSwitch to French
Documentation
  • Folder icon closed Folder open iconQuick start guide >
  • Folder icon closed Folder open iconMerchant, accounts and sales channels
    • Merchant Profilemerchant
    • Customer profilescustomer
    • Retail locationspointOfSale
    • Payment accountswallet
    • EM Accountswallet
    • Payoutspayout
    • Exit bank accountsbankAccount
  • Folder icon closed Folder open iconAutomations, integrations and exports
    • Email/SMS notifications
    • Anti-fraud services
    • File Import
    • Accounting Exports
    • Data Exports
    • Webhooks
  • Folder icon closed Folder open iconPayment Links
    • General information
    • Payment requestspaymentRequest
    • Payment page (SmartForm)
    • Callbacks, statuses and hooks
  • Folder icon closed Folder open iconCard transaction
    • General information
    • CUSTOM payment form
    • 3DS 2.0 Authentication
    • Card Transactiontransaction
    • Recurring Card Transactiontransaction
    • Card transaction via walletApplePay / GooglePay
    • Card Refund Transactionrefund / credit / dispute
    • Confirmation email
    • Bank statement descriptor
    • Currency management
    • Virtual Card Management (VCC)
    • Callbacks, statuses and hooks
  • Folder icon closed Folder open iconBank Transfer Transaction
    • General information
    • Virtual IBANs
    • Bank Transfer TransactionsctTransaction
    • Pay by Bank – Payment Initiation (PIS)
    • Reconciliation of a payment requestbankReconciliation
    • SCT R-transactionrefund
    • International wire transfers
    • Responses, statuses, and webhooks
  • Folder icon closed Folder open iconSEPA direct debit transaction
    • General information
    • SEPA Creditor ID
    • Bank account statementbankAccount
    • Creating a SEPA direct debit mandate
    • Direct Debit transactionsddTransaction
    • SDD R-Transactionrefund / sddTransactionReversal
    • Responses, statuses, and webhooks
  • Folder icon closed Folder open iconRecurring payments
    • Subscriptionsubscription
    • Installmentinstallment
  • Folder icon closed Folder open icon3DS 2.2 authentication
    • Transaction Initiated by the Holder (CIT – BRW)
    • Merchant-initiated transaction (MIT – 3RI)
    • Optimize the Frictionless Rate
    • FAQ – 3DS 2.2
  • Folder icon closed Folder open iconMerchant management
    • General information
    • Enrollment requestmerchant-enrollment
    • Complete an enrollmentmerchant-enrollment
    • Enrollment validation
    • Limited Electronic Money Accountcustomer / wallets
    • Remove the limit on an Electronic Money Accountmerchant-enrollment
    • Responses, articles of association, and webhooks
  • Folder icon closed Folder open iconPayouts
    • General information
    • Independent transfertransfer / transferReversal
    • Transfer via Transaction or PaymentRequesttransaction / paymentRequest
    • Payout to a Third Party
    • Responses, statuses, and webhooks
  • Folder icon closed Folder open iconCMS Plugin
    • WooCommerce
    • PrestaShop
    • Magento
  • Folder icon closed Folder open iconBest practices
    • VAT Returns by Country
    • Merchant-Initiated Transaction (MIT)
    • Verification of Payee (VoP)
      • FAQ – Verification of Payee

Remove the limit on an Electronic Money Account

Estimated reading: 6 minutes

A Wallet can be converted into a verified account (with limits removed) via a full onboarding process triggered by the API.

1. Step 1 – Create an enrollment

  • POST /merchant-enrollments

You must include the walletId from the existing limited wallet.

Required fields

FieldTypeDescriptionNote
walletIdUUIDLink to the EM Wallet to remove the limitValid UUID
profile[firstname][value]string (255)First nameAlpha + -
profile[lastname][value]string (255)NameAlpha + -
profile[email][value]string (255)Contact email—
profile[phone][value]string (15)International phone—
profile[birthday][value]date (YYYY-MM-DD)Date of birthBetween 18 and 110 years old
profile[place_of_birth][value]string (255)Birthplace—
profile[country_of_birth][country]string (3)Country of birthISO 3166-1 alpha-3
languagestring (3)"fr" or "en"—
accountTypestring"BASIC"—
typestring"INDIVIDUAL"—
activitySectorUUID (36)Activity sectorGET /api/nauth/enrollment-claim/activity-sector
feeScheduleUUID (36)Price gridPOST /api/merchant-enrollment/fee-schedule
turnoverUUID (36)Expected annual revenuePOST /api/nauth/enrollment-claim/turnover
workflowDefinitionUUIDWorkflow templateprovided by CentralPay
profileWorkflowDefinitionUUIDProfile templateprovided by CentralPay
workflowModestring"SEQUENTIAL"Required
allowedEmailCommunicationbooleanConsentement à recevoir des emailstrue or false

Optional fields

FieldTypeDescription
sendClaimEmailbooleanSending the enrollment email (default: true)
sendProfileCreationEmailbooleanEmail after profile completion
sendAccountCreationEmailbooleanEmail upon opening a verified account
customReferencestringInternal reference
technicalContact, administrativeContact, financialContactstring(255)Business contacts
addSecurityReferencebooleanDisplays a safety reference (for STANDARD, PARTNER, RESELLER)
hookUUIDTechnical hook
birthdayConfirmation[value]dateIf affiliated with an agent

2. Step 2 – Complete a KYC enrollment (via autocomplete)

To speed up the enrollment process, you can fill out all the required information at once by calling:

  • POST /merchant-enrollment/{uuid}/autocomplete

Residential address

FieldTypeRequiredDescriptionNote
address[nameLine1]string✅ YesStreet number and name—
address[locality]string✅ YesCity of residence—
address[postalCode]string✅ YesPostal code—
address[country]string✅ YesCountry of residenceISO 3166-1 alpha-3

Identification document

FieldTypeRequiredDescriptionNote
identityDocument[type]string✅ YesDocument typeIDENTITY_CARD, PASSPORT, RESIDENCE_PERMIT, VISA, IDENTITY_DOCUMENT_RECEIPT
identityDocument[documents][0]file✅ YesFront side or main scanJPG, JPEG or PNG
identityDocument[documents][1]file✅ Yes, if IDENTITY_CARDBack side or additional pageJPG, JPEG or PNG
identityDocument[issuingCountry]string✅ YesIssuing countryISO 3166-1 alpha-3
identityDocument[expiryDate]string❌ NoExpiration dateFormat YYYY-MM-DD
identityDocument[checkId]string❌ NoControl ID (Onfido)—
identityDocument[documentNumber]string❌ NoDocument number—
identityDocument[mrzLine1]string❌ NoMRZ 1 Line—
identityDocument[mrzLine2]string❌ NoMRZ 2 Line—

Special cases

FieldRequiredConditionDescription
identityDocument[proofOfIdentityDocument]✅ Yesif type = IDENTITY_DOCUMENT_RECEIPTVisual proof of receipt
identityDocument[proofOfIdentityDocuments][*]✅ YeslikewiseMultiple files, if applicable
identityDocument[proofOfIdentityDocumentExpiryDate]✅ Yesif file proofOfIdentityDocument providedFormat YYYY-MM-DD

Banking information (optional but recommended)

FieldTypeRequiredDescriptionNote
iban[value]string❌ NoIBAN to be verifiedValid IBAN format
bic[value]string❌ NoBIC/SWIFT code—
ibanDocument[document]file❌ NoProof of bank information (bank account details, statement)JPG, JPEG or PNG

Additional KYC data (riskData)

All of the following fields are required unless otherwise noted.

FieldTypeRequiredDescriptionNote
riskData[isPep]bool✅ YesPolitically exposed person?default: false
riskData[isInSanctionList]bool✅ YesIs it on a sanctions list?default: false
riskData[residentAlpha3Code]string✅ YesCountry of residenceISO 3166-1 alpha-3
riskData[isHighRiskResident]bool✅ YesCountry of residence at risk?—
riskData[nationalityAlpha3Code]string✅ YesNationalityISO 3166-1 alpha-3
riskData[isHighRiskNationality]bool✅ YesNationality at risk?—
riskData[isHighRiskMCCActivitySector]bool✅ YesIs the MCC sector at risk?—
riskData[MCCActivitySector]int✅ YesMCC code (NAF or sector)—
riskData[monthlyLimit]int✅ YesReported monthly limit (in centimes)E.g., 150000 = €1,500.00
riskData[monthlyLimitCurrencyAlphabeticCode]string✅ YesCurrency (e.g., EUR)ISO 4217
riskData[isCrossBorderPayment]bool❌ NoCross-border payments?Default: true
riskData[declaredMonthlyRevenue]int❌ NoReported income (in centimes)—
riskData[verifiedMonthlyRevenue]int✅ Yes, if full KYCVerified incomes—

Additional documents (if required)

FieldTypeRequiredDescriptionNote
proofOfAddressDocument[documents][0]file✅ Yes, if the profile is at riskProof of addressJPG, JPEG or PNG
incomeDocument[document]file✅ Yes, if full KYC is requiredProof of income (1 document)JPG, JPEG or PNG
incomeDocument[documents][*]file✅ Yes, if full KYC is requiredMultiple files allowedJPG, JPEG or PNG

Other documents (if necessary to lift the limit)

FieldTypeDescriptionNotes
additionalDocuments[X]['type']stringType of document submittedEx: UBO_DECLARATION, PROOF_OF_VAT_REGISTRATION, LICENSING_AGREEMENT, etc.
additionalDocuments[X]['documents'][X]fileFiles submittedFile format: JPG, JPEG, PNG
ℹ️ The complete list of accepted document types is documented in the Open API.

Open data (required, even if empty)

FieldTypeRequiredDescription
metaDataJSON object✅ YesOpen metadata, in {"key": "value"} format (may be empty)

3. Step 3 – Correcting a failed enrollment (autoupdate)

If the compliance department rejects one or more documents (e.g., a blurry ID card, an expired document), you can submit only the rejected items via a self-update request.

  • POST /merchant-enrollment/{uuid}/autoupdate

Correction of an identification document

FieldTypeRequiredDescriptionNote
identityDocument[type]string✅ YesType of document to be correctedIDENTITY_CARD, PASSPORT, RESIDENCE_PERMIT, VISA, IDENTITY_DOCUMENT_RECEIPT
identityDocument[documents][0]file✅ YesFront side of the document (or single file)JPG, JPEG or PNG
identityDocument[documents][1]file✅ Yes, if type = IDENTITY_CARDBack side of the NICJPG, JPEG or PNG
identityDocument[issuingCountry]string✅ Yes, if the document is submittedIssuing countryISO 3166-1 alpha-3

Additional identification document (if required)

FieldTypeRequiredDescription
complementaryIdentityDocument[documents][0]file✅ Yes, if requiredAdditional scan or photo
complementaryIdentityDocument[expiryDate]string✅ YesExpiration date (YYYY-MM-DD)
complementaryIdentityDocument[documentNumber]string✅ YesDocument number
complementaryIdentityDocument[mrzLine1]string✅ YesMRZ Line 1
complementaryIdentityDocument[mrzLine2]string✅ YesMRZ Line 2
complementaryIdentityDocument[issuingCountry]string✅ YesIssuing country (ISO alpha-3)

Income documents

FieldTypeRequiredDescription
incomeDocument[document]file✅ Yes, if requiredSingle JPG/JPEG/PNG file
incomeDocument[documents][*]file✅ Yes, if multiple are expectedMultiple documents by index ([0], [1], etc.)

Additional personal information

FieldTypeRequiredDescription
profile[firstname][value]string❌ NoFirst name
profile[lastname][value]string❌ NoName
profile[birthday][value]string❌ NoDate of birth
profile[place_of_birth][value]string❌ NoBirthplace
profile[country_of_birth][country]string❌ NoCountry of birth (ISO 3166-1 alpha-3)

Address correction (if rejected)

FieldTypeRequiredDescription
profile[address][nameLine1]string❌ NoAddress – line 1
profile[address][postalCode]string❌ NoPostal code
profile[address][country]string❌ NoCountry (ISO alpha-3)
profile[address][locality]string❌ NoCity

Updating KYC data (riskData)

All of the following fields are required unless otherwise noted. They must be returned exactly as they are or updated if changed as part of the correction.

FieldTypeRequiredDescriptionNote
riskData[isPep]boolean✅ YesPEP?default: false
riskData[isInSanctionList]boolean✅ YesOn a sanctions list?default: false
riskData[residentAlpha3Code]string✅ YesCountry of residenceISO alpha-3
riskData[isHighRiskResident]boolean✅ YesCountry of residence at risk?—
riskData[nationalityAlpha3Code]string✅ YesNationalityISO alpha-3
riskData[isHighRiskNationality]boolean✅ YesNationality at risk?—
riskData[isHighRiskMCCActivitySector]boolean✅ YesHigh-risk area?—
riskData[MCCActivitySector]int✅ YesMCC business code—
riskData[monthlyLimit]int✅ YesMonthly limit (in centimes)[0 ; 190000]
riskData[monthlyLimitCurrencyAlphabeticCode]string✅ YesCurrency (e.g., EUR)ISO 4217
riskData[isCrossBorderPayment]boolean❌ NoCross-border paymentsdefault: true
riskData[declaredMonthlyRevenue]int❌ NoReported incomes—
riskData[verifiedMonthlyRevenue]int✅ Yes, if full KYCVerified incomes (centimes)

Additional documents (optional or required)

FieldTypeRequiredDescription
additionalDocuments[X]['type']string✅ Yes, if the documents are expectedType of proof
additionalDocuments[X]['documents'][X]file✅ YesRelated files (JPG, JPEG, PNG)

Other fields

FieldTypeRequiredDescription
fullKycboolean❌ NoAllows you to require full or simplified KYC (true / false)

4. Step 4 – Track the status of an enrollment

Once an enrollment has been created and completed, you can check its status at any time to:

  • Check the status (ON_GOING, ACCEPTED, REFUSED)
  • Track pending steps in the workflow
  • Extract previously submitted profile data

Retrieve an enrollment

GET /merchant-enrollment/{enrolmentId}

Required settings

FieldTypeRequiredDescriptionNote
enrolmentIdUUID (36)✅ YesEnrollment ID returned upon creation (POST /merchant-enrollments)Standard UUID format
ℹ️ The enrollment must belong to the scope authorized by your API credentials (merchant or sub-merchant).

Main fields in the response

FieldTypeDescription
uuidUUIDUnique enrollment ID
workflow.statusstringProcess status (ON_GOING, ACCEPTED, REFUSED)
workflow_modestring"SEQUENTIAL" or "CONTINUAL"
workflow.activities[]tableList of activities (steps) still to be completed
profile[...]objectProfile data that has already been submitted, with their status
conformity_statusstringOverall compliance status (ON_GOING, REVIEW, APPROVED, etc.)
created_atdatetimeEnrollment creation date
activity_sector.namestringSector reported on the enrollment form

Keep an eye on

  • As long as an activity has a state = TODO, enrollment is incomplete
  • When there are no pending activities and workflow.status = ACCEPTED, the user is approved
  • In case of workflow.status = REFUSED, no verified wallet will be generated

5. KYC verification process for a ME account

Remove the limit on an Electronic Money Account - PreviousLimited Electronic Money AccountNext - Remove the limit on an Electronic Money AccountResponses, articles of association, and webhooks
CONTENTS

Doc Contents

Doc Footnotes

Doc Elements

  • Legal notices
  • Privacy policy

© 2026 CentralPay

You must log in to continue.

Login to CentralPay Documentation

Forgotten account?

Reset your password

Enter your username or email address and we will send you a link to reset your password.

Back to login
  • French