Phase 3 — Organisation Documents & T&Cs
Steps 8–9 of reseller onboarding — upload the KYB business documents and record the merchant's signed terms and website URL.
Part of Merchant Acquiring Reseller — Phase 3 of 6 · Actor: ResellerUpload all KYB-required business documents against the organisation, plus the merchant's signed terms and website URL. Everything here must be in place before ratification is submitted in Phase 4.
Step 08 — Upload organisation business documents
All KYB-required business documents are uploaded against the organisation record. One call per document. All documents must be in place before ratification is submitted in Step 12.
Actor: Reseller
POST /eclipse-conductor/rest/v1/tenants/{tenantId}/organisations/{organisationId}/documents📎 API reference: Add a document to the organisation
| Field | Notes |
|---|---|
documentType | See supported types below |
base64EncodedDocument | Base64-encoded file content |
mediaType | image/jpeg · image/png · application/pdf |
extraInfo | Optional metadata or context note |
performOcr | Query param — enables OCR on upload |
validateDocType | Query param — verifies content matches the declared type (requires performOcr=true) |
Mandatory — all business types
CERT_OF_INCORP or CERT_OF_REGISTRATION · PROOF_OF_ADDRESS · TAX · BANK_ACCOUNT_CONFIRMATION · BANK_STATEMENT (Source of Funds)
Sole Proprietor — no registered company
CERT_OF_INCORPandCERT_OF_REGISTRATIONare not applicable. Upload the owner's personal KYC documents at the customer level (ID, proof of address) in Phase 2, Step 05, plus aTAXdocument (SARS income tax reference) at the organisation level. The KYB ruleset relies on the positional holder's KYC data in lieu of a company registration certificate.
CERT_OF_INCORPvsCERT_OF_REGISTRATION
CERT_OF_REGISTRATIONis the correct type for CIPC-issued documents. UseCERT_OF_INCORPif the tenant's KYB ruleset references that specific field name — they serve the same purpose.
Optional — supported document types
BUSINESS_LICENSE · PARTNERSHIP_DEED · TRUST_DEED · LOGO · PROOF_OF_FUNDS · ENHANCED_DUE_DILIGENCE · USA_W_8 · USA_W_9 · AFFIDAVIT
Step 09 — Upload signed T&Cs and website URL as organisation attachments
Records merchant acceptance of EFT Corporation terms and the merchant's website URL. Two attachments — call the endpoint twice.
Actor: Reseller
POST /eclipse-conductor/rest/v1/tenants/{tenantId}/organisations/{organisationId}/attachments📎 API reference: Add an attachment to the organisation — supported media types: application/pdf, image/png, image/jpeg, application/json, text/plain.
Call 1 — Signed T&Cs
| Field | Notes |
|---|---|
attachmentType | terms.and.conditions |
base64EncodedAttachment | Base64-encoded signed PDF (up to 5 MB) |
fileName | Original filename (5–200 chars) |
mediaType | application/pdf |
info | Optional — e.g. acceptance date in ISO 8601 |
Call 2 — Website URL
| Field | Notes |
|---|---|
attachmentType | website.url |
info | The merchant's website URL e.g. https://www.merchantsite.co.za |
base64EncodedAttachment | Not required — omit for URL-only attachments |
Website URL — interim locationThe website URL is required by compliance for the website audit in Phase 6, Step 17. It will become a dedicated field on the organisation creation endpoint in a future Eclipse API release — for now, record it as a
website.urlattachment.
Navigation
- ◀ Previous: Phase 2 — Customer Registration & Positions
- ▲ Overview: Merchant Acquiring Reseller
- ▶ Next: Phase 4 — Verification & KYB Submission