Phase 4 — Verification & KYB Submission
Steps 10–13 of reseller onboarding — set the MCC, validate the bank account via AVS, submit KYB ratification, and create the (barred) wallet.
Part of Merchant Acquiring Reseller — Phase 4 of 6 · Actor: ResellerConfirm the merchant category code, validate the bank account, submit KYB ratification, and create the wallet. The wallet is created in
BARREDstatus and is unbarred later by compliance in Phase 6.
Step 10 — Assign MCC
Set or confirm the merchant category code. The value is validated against the tenant's allowed list — codes not on the list are rejected.
Actor: Reseller
PUT /eclipse-conductor/rest/v1/tenants/{tenantId}/organisations/{organisationId}📎 API reference: Update an organisation by ID
| Field | Notes |
|---|---|
categoryCode | 4-digit MCC integer e.g. 5411 |
businessWebsite | Set or update the merchant's website URL, e.g. https://www.merchantsite.co.za |
The allowed list is held in the tenant config public.industrial.classification.allowed.values.{tenantId}.
If categoryCode was already set during organisation creation in Phase 1, Step 01, this call is only needed to update it.
Step 11 — Validate bank account via AVS
Account Verification Service validates that the supplied bank account details belong to the registered organisation. Pass onlyCheck=true to validate without creating a beneficiary record.
Actor: Reseller
POST /eclipse-conductor/rest/v1/tenants/{tenantId}/organisations/{organisationId}/beneficiaries?onlyCheck=true📎 API reference: Add a beneficiary to the organisation
| Field | Notes |
|---|---|
accountHolderName | Full name on the account (2–50 chars) |
firstName | Account holder first name |
lastName | Account holder surname |
bankAccountNumber | Account number |
branchCode | Bank branch / sort code |
accountType | CURRENT · SAVINGS · TRANSMISSION |
identityNumber | SA ID of the account holder |
identityType | SID (SA ID) · SPP (Passport) · SBR (Business Reg) · TRN (Tax) |
Account details must match the uploaded bank statement document exactly. If validation passes and you want to persist the beneficiary record, repeat the call with saveOnPass=true.
AVS result
completeMatch | Meaning | Action |
|---|---|---|
Y | All fields matched | Proceed |
N | One or more fields did not match | Inspect individual field results in the response |
U | Unprocessed (AVS service unavailable or non-responsive) | Retry, or escalate via Support |
Step 12 — Submit KYB ratification
Triggers the automated screening pipeline. All document uploads from Phase 2, Step 05 and Phase 3, Step 08 must be complete before this call.
Actor: Reseller
POST /eclipse-conductor/rest/v1/tenants/{tenantId}/organisations/{organisationId}/ratify
GET /eclipse-conductor/rest/v1/tenants/{tenantId}/organisations/{organisationId}/ratify📎 API reference: Run KYB ratification on the organisation · Get KYB ratification results
| Field | Notes |
|---|---|
type | NORMAL · COMPARISON |
Submit with type: NORMAL. Poll the GET endpoint until results are populated.
Sole Proprietors (SOLE_PROPRIETOR) — KYB is not requiredSole Proprietor merchants do not run organisation KYB ratification. Instead, run KYC on the owner (customer) and then proceed directly to wallet creation (Step 13) using the Sole Proprietor wallet type.
POST /eclipse-conductor/rest/v1/tenants/{tenantId}/customers/{customerId}/ratify📎 API reference: Run KYC on a customer
Retrieving the latest resultResults are returned most-recent first. Pass
offset=0&limit=1to fetch only the latest. A v2 results endpoint is also available.
Possible outcomes
| Result | Meaning |
|---|---|
passed: true | Proceed to wallet creation in Step 13 |
passed: false | Review the populated itemResults array — each entry identifies the failing check |
| Sanctions hits found | The case routes to manual compliance review in Phase 6 |
Step 13 — Create the organisation wallet
This call triggers the KYB ruleset evaluation. The ruleset reads the latest ratification result, runs KYC on all DIRECTOR positions, and if all checks pass creates the wallet in BARRED status. Compliance unbars it in Phase 6.
Actor: Reseller
POST /eclipse-conductor/rest/v1/tenants/{tenantId}/organisations/{organisationId}/wallets📎 API reference: Create a wallet for the organisation
| Field | Notes |
|---|---|
walletTypeId | Provided by EFT Corporation — specific to your tenant arrangement and the merchant's business type |
Wallet type differs by business typeThe
walletTypeIddepends on the merchant's business type — use the Sole Proprietor wallet type forSOLE_PROPRIETORmerchants and the Limited Company wallet type forLIMITED_COMPANYmerchants. EFT Corporation provides the correctwalletTypeIdfor each.
Create only one wallet per merchantExactly one wallet must be created per merchant organisation. Do not create additional wallets for the same merchant.
Ratification must pass firstFor company structures, the KYB ruleset must find a passing ratification result from Step 12. If ratification has not been run, or the last result was not a pass, this call is rejected by the ruleset with the message
Please do KYB in order to create the wallet for this ruleset.For Sole Proprietors, a passing customer KYC result (Step 12) is used instead of KYB.
Next: accept T&Cs, then submit for reviewAfter the wallet is created, the merchant accepts the Terms & Conditions digitally (Phase 6, Step 16), then you submit the case for EFT Corporation compliance review (Phase 6, Step 17). The submit-for-review call is reused any time you later change the merchant record and need it re-reviewed.
Navigation
- ◀ Previous: Phase 3 — Organisation Documents & T&Cs
- ▲ Overview: Merchant Acquiring Reseller
- ▶ Next: Phase 5 — Automated Screening
Updated about 19 hours ago