Merchant Acquiring Reseller

Summary

This page is the canonical onboarding reference for resellers integrating with the Eclipse API. It takes you from an empty merchant record all the way to a live, transacting wallet, covering every API call, document type, and screening check along the way.

In short, onboarding a merchant means: create the legal entity, register and verify the people behind it (directors, owners, UBOs), attach the business documents, submit the case for automated KYB screening, and finally have the merchant accept the Terms & Conditions and have EFT Corporation compliance review and activate the wallet. The work is split across 6 phases and 20 ordered steps, shared between 3 actors — you (the Reseller), the automated platform (System), and the EFT Corporation Compliance team.

Two things are worth internalising before you start. First, the flow is strictly ordered — most steps depend on data captured earlier, so gaps cannot be repaired at the end. Second, a new wallet is always created in a BARRED state; only compliance can unbar it once screening and the website audit have cleared.

flowchart TD
    subgraph Reseller
        P1["Phase 1 — Organisation Setup<br/>Steps 1–2"]
        P2["Phase 2 — Customer Registration & Positions<br/>Steps 3–7"]
        P3["Phase 3 — Org Documents & Website<br/>Steps 8–9"]
        P4["Phase 4 — Verification & KYB Submission<br/>Steps 10–13"]
    end
    subgraph System
        P5["Phase 5 — Automated Screening<br/>Steps 14–15"]
    end
    subgraph Compliance
        P6["Phase 6 — Compliance Review & Activation<br/>Steps 16–20"]
    end
    P1 --> P2 --> P3 --> P4 --> P5 --> P6
    P6 --> Live(["Live, unbarred wallet"])

📘

How this guide is organised

Each phase is a separate page. Work through them in order, or jump to the phase you need using the navigation below. The final page collects every field, document type, and status code in one place for quick lookup.

---

The flow is ordered

Most steps depend on prior ones. Skipping a step (for example, omitting companyNumber at organisation creation, or not assigning a DIRECTOR position before submitting ratification) causes the KYB ruleset to fail or routes the case to manual compliance review. Plan your UX to enforce the data minimums at the point of collection rather than trying to repair gaps at submission.

---

At a glance

Actors

---

Phases — navigation

Reference: Field, document, and code quick reference — every field, document type, position, and status code in one place, plus operational and security reminders.

---

What's next

• Start with Phase 1 — Organisation Setup
• Support and escalations → Support