Your systems connect once, and we keep them connected.
From payments and finance to learning platforms and your Microsoft estate — MemEx API is the single layer everything connects through, built, tested and maintained by us.
MemEx API is the integration layer of MemEx, built by Wattle, connecting payment providers, learning platforms and the wider Microsoft estate to MemEx CRM through one versioned API.
Frequently asked
Yes, through MemEx API — the integration layer that connects payment providers, finance and accounting systems, learning platforms and the wider Microsoft estate to MemEx CRM.
MemEx API — the published interface, its controllers and the version history beside them.
The approach
One interface, maintained in one place
The website, the portal and every system you connect all work against the same versioned interface. Integration is defined, tested and maintained in one place, and one supplier is accountable for it.
Most membership estates are joined together pair by pair instead — the website to the CRM, the portal to the CRM, the CRM to finance — and every join has to be revisited when either end changes. That is the cost MemEx API removes.
Integrations
What it connects to
Payments
Six providers, including Stripe, GoCardless, Opayo with 3D Secure, Paysafe and Authorize.Net. Cards, direct debit mandates, payment plans and refunds all post back against the invoice they belong to.
Learning and assessment
Canvas LMS and Rogo, so course activity and exam results reach the member record without anyone exporting a spreadsheet.
The Microsoft estate
SharePoint for documents, Azure Blob for storage, and Azure AD B2C for member identity.
Public data
Companies House, for organisational membership and employer records.
Reliability
Built to be depended on
Every channel works against the versioned interface rather than against CRM internals, which is what stops the estate breaking when the CRM changes.
Single identity
Member identity runs through Azure AD B2C, so a member signs in once and is the same person everywhere.
Resilient data access
Data access runs against Dataverse with caching and retry, so a renewal peak does not become an outage.
Asynchronous by design
Asynchronous work runs over Service Bus with webhook listeners and scheduled functions, so long jobs never hold up a member.
Tested and shipped through a pipeline
Acceptance tests and a unit test suite run against every change, and releases ship through a pipeline rather than by hand.
MemEx API — the release pipeline and test run, green, with the version history of the interface beside it.
Open platform
Your own developers can build on it
The API is documented and published. Your team, or a partner you choose, can read from it and build against it. Webhooks let your systems react to what happens in membership as it happens, without polling for changes.
Bring us your integration list.
Book a demo, or talk it through with the engineers who built the interface.