Evoxup Integrations — Universal Provider Integration for WordPress
:root{
--bg:#fff;--soft:#f5f8ff;--soft2:#eef3ff;--ink:#0a1222;--muted:#5d6b82;
--line:#dce5f5;--blue:#1769ff;--blue2:#0e48bd;--blue3:#0b2c71;--crimson:#d7263d;
--dark:#07111f;--dark2:#0c1930;--radius:22px;--shadow:0 18px 50px rgba(20,62,125,.10)
}
*{box-sizing:border-box}
html{scroll-behavior:smooth}
body{margin:0;font-family:Inter,ui-sans-serif,-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Arial,sans-serif;color:var(--ink);background:var(--bg);line-height:1.65}
a{color:inherit;text-decoration:none}.container{width:min(1180px,calc(100% - 40px));margin:auto}
h1,h2,h3{line-height:1.12;margin:0 0 18px}
h1{font-size:clamp(3rem,6vw,6rem);letter-spacing:-.055em}
h2{font-size:clamp(2rem,4vw,4rem);letter-spacing:-.045em}
h3{font-size:1.25rem}
p{margin:0 0 18px;color:var(--muted)}.lead{font-size:clamp(1.08rem,1.6vw,1.32rem);max-width:800px}
.eyebrow{display:inline-flex;align-items:center;gap:9px;font-size:.78rem;font-weight:800;letter-spacing:.13em;text-transform:uppercase;color:var(--blue)}
.eyebrow:before{content:"";width:28px;height:2px;background:var(--crimson);border-radius:3px}
.btn{display:inline-flex;align-items:center;justify-content:center;min-height:50px;padding:0 22px;border-radius:13px;font-weight:800;border:1px solid transparent;transition:.2s}
.btn.primary{background:var(--blue);color:#fff;box-shadow:0 12px 28px rgba(23,105,255,.25)}
.btn.secondary{background:#fff;border-color:var(--line)}
.btn:hover{transform:translateY(-2px)}
.badge{display:inline-flex;padding:5px 10px;border-radius:999px;font-size:.7rem;font-weight:850;background:#eaf1ff;color:var(--blue2)}
header{position:sticky;top:0;z-index:20;background:rgba(255,255,255,.9);backdrop-filter:blur(18px);border-bottom:1px solid rgba(220,229,245,.8)}
.nav{height:74px;display:flex;align-items:center;justify-content:space-between;gap:20px}
.brand{display:flex;align-items:center;gap:10px;font-weight:900}
.brandmark{width:34px;height:34px;border-radius:11px;background:linear-gradient(145deg,var(--blue),var(--blue3));position:relative}
.brandmark:after{content:"";position:absolute;width:10px;height:10px;border-radius:50%;background:var(--crimson);right:-3px;bottom:4px;border:3px solid white}
.navlinks{display:flex;gap:24px;font-weight:700;font-size:.93rem;color:#30405a}
.navlinks a.active,.navlinks a:hover{color:var(--blue)}
.navright{display:flex;gap:10px;align-items:center}
.hero{padding:105px 0 82px;position:relative;overflow:hidden;background:
radial-gradient(circle at 88% 14%,rgba(23,105,255,.15),transparent 28%),
radial-gradient(circle at 8% 26%,rgba(215,38,61,.08),transparent 18%),
linear-gradient(180deg,#fff,#f8fbff)}
.hero:before{content:"";position:absolute;inset:0;opacity:.28;background-image:linear-gradient(#dce5f5 1px,transparent 1px),linear-gradient(90deg,#dce5f5 1px,transparent 1px);background-size:42px 42px;mask-image:linear-gradient(to bottom,black,transparent 72%)}
.hero-grid{position:relative;display:grid;grid-template-columns:1.05fr .95fr;gap:54px;align-items:center}
.hero h1 span{color:var(--blue)}
.actions{display:flex;gap:12px;flex-wrap:wrap;margin-top:28px}
.arch{padding:26px;border-radius:30px;background:linear-gradient(150deg,#07111f,#0e2c63);box-shadow:0 30px 80px rgba(7,17,31,.25);color:#fff}
.arch-title{font-size:1.22rem;font-weight:850;margin-bottom:16px}
.provider-grid{display:grid;grid-template-columns:repeat(2,1fr);gap:12px}
.provider{padding:15px;border:1px solid rgba(255,255,255,.12);border-radius:16px;background:rgba(255,255,255,.05);font-weight:800}
.provider small{display:block;color:#94a9c9;margin-top:4px;font-weight:600}
.flowarrow{text-align:center;color:#7e98c6;font-size:1.5rem;margin:12px 0}
.core{padding:19px;border-radius:18px;background:linear-gradient(130deg,var(--blue),var(--blue2));font-weight:850}
.core small{display:block;color:#d9e7ff;font-weight:600;margin-top:4px}
.output-grid{display:grid;grid-template-columns:repeat(3,1fr);gap:9px;margin-top:12px}
.output{padding:12px;text-align:center;border:1px solid rgba(255,255,255,.11);border-radius:13px;background:rgba(255,255,255,.05);font-size:.82rem;font-weight:750}
.anchorbar{border-top:1px solid var(--line);border-bottom:1px solid var(--line);background:#fff}
.anchorrow{display:flex;gap:10px;flex-wrap:wrap;padding:18px 0}
.anchorrow a{padding:8px 12px;border-radius:10px;border:1px solid var(--line);font-size:.85rem;font-weight:800;color:#44546d;background:#fff}
section{padding:100px 0}.soft{background:var(--soft)}.dark{background:linear-gradient(135deg,#07111f,#0a1d3b);color:#fff}
.dark h2,.dark h3{color:#fff}.dark p{color:#aabbd4}
.section-head{max-width:860px;margin-bottom:48px}
.grid4{display:grid;grid-template-columns:repeat(4,1fr);gap:18px}
.grid3{display:grid;grid-template-columns:repeat(3,1fr);gap:20px}
.card{padding:26px;border:1px solid var(--line);border-radius:var(--radius);background:#fff;box-shadow:0 8px 28px rgba(28,64,117,.04)}
.icon{width:46px;height:46px;border-radius:14px;background:#edf3ff;color:var(--blue);display:grid;place-items:center;font-weight:900;margin-bottom:18px}
.darkcard{padding:24px;border-radius:20px;background:#0c1b32;border:1px solid #1c3152}
.darkcard .icon{background:#122d59;color:#9cc0ff}
.split{display:grid;grid-template-columns:1fr 1fr;gap:54px;align-items:center}
.visual{border:1px solid var(--line);border-radius:26px;background:#fff;box-shadow:var(--shadow);overflow:hidden}
.visualbar{height:46px;background:#f4f7fb;border-bottom:1px solid var(--line);display:flex;align-items:center;gap:7px;padding:0 15px}
.dot{width:8px;height:8px;border-radius:50%;background:#c5d0e1}.visualbody{padding:22px}
.row{padding:14px 0;border-bottom:1px solid #edf1f7;display:flex;align-items:center;justify-content:space-between;gap:10px}
.row:last-child{border-bottom:0}
.status{padding:4px 9px;border-radius:999px;font-size:.68rem;font-weight:850}
.ok{background:#e7f8ee;color:#187447}.warn{background:#fff1f2;color:#aa3041}
.chips{display:flex;flex-wrap:wrap;gap:9px;margin:20px 0}
.chips span{padding:8px 11px;border:1px solid var(--line);border-radius:10px;font-size:.82rem;font-weight:750;color:#34435b}
.process{display:grid;grid-template-columns:repeat(6,1fr);gap:11px;margin-top:30px}
.step{padding:18px;border:1px solid var(--line);border-radius:16px;background:#fff;position:relative}
.step:after{content:"→";position:absolute;right:-11px;top:50%;transform:translateY(-50%);color:#9cacbf;font-weight:900}
.step:last-child:after{display:none}
.step b{display:block;margin-bottom:4px}.step small{color:#66758d}
.profile-grid{display:grid;grid-template-columns:repeat(4,1fr);gap:18px}
.profile{border:1px solid var(--line);border-radius:22px;background:#fff;padding:24px;position:relative;overflow:hidden}
.profile:before{content:"";position:absolute;width:120px;height:120px;border-radius:50%;background:rgba(23,105,255,.06);right:-40px;top:-40px}
.profile h3{font-size:1.35rem;margin-top:14px}.profile ul{padding-left:18px;color:#55657b}.profile li{margin:7px 0}
.profile.custom{border:2px solid var(--blue)}
.tablewrap{overflow:auto;border:1px solid var(--line);border-radius:20px;background:#fff}
table{width:100%;border-collapse:collapse;min-width:820px}
th,td{padding:16px 18px;text-align:left;border-bottom:1px solid #edf1f7}
th{background:#f7f9fd;font-size:.82rem;text-transform:uppercase;letter-spacing:.05em;color:#44546d}
td{color:#52627a;font-size:.92rem}
.yes{color:#187447;font-weight:850}.depends{color:#a66a00;font-weight:850}
.timeline{display:grid;gap:14px}
.timeline-item{display:grid;grid-template-columns:50px 1fr;gap:14px;align-items:flex-start}
.num{width:42px;height:42px;border-radius:13px;background:#edf3ff;color:var(--blue);display:grid;place-items:center;font-weight:900}
.band{padding:28px;border-radius:24px;background:linear-gradient(120deg,var(--blue),var(--blue2));color:#fff;display:flex;justify-content:space-between;gap:20px;align-items:center;margin-top:32px}
.band p{color:#e6efff;margin:5px 0 0}
.cta{padding:86px 0;background:radial-gradient(circle at 20% 20%,rgba(23,105,255,.22),transparent 30%),linear-gradient(135deg,#07111f,#102a5a);color:#fff}
.cta h2{color:#fff}.cta p{color:#b9c9e1}
footer{background:#050b14;color:#a6b5ca;padding:55px 0 26px}
.footgrid{display:grid;grid-template-columns:1.4fr repeat(4,1fr);gap:30px}
footer h4{color:#fff;margin:0 0 13px}footer a{display:block;margin:8px 0;font-size:.9rem}
.footnote{border-top:1px solid #172238;margin-top:34px;padding-top:20px;font-size:.82rem;color:#73839d}
@media(max-width:980px){
.navlinks{display:none}.hero-grid,.split{grid-template-columns:1fr}.grid4,.profile-grid{grid-template-columns:repeat(2,1fr)}
.grid3{grid-template-columns:repeat(2,1fr)}.process{grid-template-columns:1fr}.step:after{display:none}.footgrid{grid-template-columns:repeat(2,1fr)}
}
@media(max-width:640px){
.container{width:min(100% - 26px,1180px)}h1{font-size:3.1rem}section{padding:72px 0}
.grid4,.grid3,.profile-grid,.provider-grid,.output-grid{grid-template-columns:1fr}.footgrid{grid-template-columns:1fr}
.band{flex-direction:column;align-items:flex-start}.navright a:first-child{display:none}
}
img,svg{display:block;max-width:100%}
.brand-mark svg{width:23px;height:23px;color:#fff}
.brand-mark{
width:38px;height:38px;border-radius:12px;
background:linear-gradient(145deg,var(--blue),var(--teal));
display:grid;place-items:center;box-shadow:0 8px 24px rgba(18,84,244,.24);
}
Universal Integrations
One Integration Layer. Any Commerce Provider.
Connect WordPress commerce, external stores and custom platforms to Evoxup through webhooks, REST APIs and provider-specific verification — without rebuilding your membership and licensing architecture for every provider.
Provider-Neutral Commerce Flow
WooCommerceWordPress commerce
GumroadReady-made provider profile
Lemon SqueezyReady-made provider profile
Custom ProviderWebhook / REST API
↓
Evoxup Universal Integration EngineReceive → Verify → Normalize → Map → Fulfill
Membership
License
Entitlements
Provider-Neutral by Design
Your Provider Should Connect to Evoxup — Not Define Evoxup.
Evoxup keeps the product, membership, licensing and entitlement logic inside your WordPress platform. Commerce providers remain interchangeable inputs to that lifecycle.
1
Keep Internal Product Logic Stable
External platforms can change while your EVO Products, Membership Plans and licensing rules remain under your control.
2
Adapt to Provider Capabilities
Use the authentication and verification method the provider actually offers instead of forcing every platform into one security model.
3
Normalize Before Fulfillment
Provider-specific events are translated into an internal workflow before product mapping and access fulfillment take place.
Provider EventSale / order / custom event
VerifySignature / API / policy
NormalizeProvider-neutral data
IdentifyResolve external product
MapFind EVO destination
FulfillMembership / license / access
Connection Methods
Different Providers. Different Security Models. One Integration Layer.
Evoxup can follow the provider's real transport and verification model instead of pretending that every integration behaves the same way.
↗
Signed Webhooks
For providers that send an HMAC signature, webhook signature or shared signing secret with incoming events.
✓
API Verification
Receive the event, then confirm transaction data against the provider API before granting access.
K
Authenticated APIs
Use provider API credentials such as API keys or bearer tokens for discovery, verification or synchronization.
≈
Unsigned Webhooks
Support providers without native signatures using a policy appropriate to the capabilities they actually expose.
Ready-Made Provider Profiles
Fast Setup for Known Providers. Universal Support Beyond Them.
Ready-made profiles reduce setup complexity for platforms Evoxup already understands. They are shortcuts — not limits on what the integration engine can connect.
WORDPRESS COMMERCE
WooCommerce
Connect WordPress commerce workflows to Evoxup products, memberships, licensing and entitlements.
- Internal WordPress commerce path
- Product-aware fulfillment
- Membership and licensing workflows
READY-MADE PROFILE
Gumroad
Use a guided provider profile for product discovery, API-based verification, mapping and fulfillment workflows.
- Provider product discovery
- API-assisted sale verification
- Product Mapping compatibility
- Product Sync compatibility
READY-MADE PROFILE
Lemon Squeezy
Use a guided provider profile with API connectivity and signed webhook handling.
- API credential
- Webhook signing secret
- Product and variant discovery
- Mapping and synchronization workflows
UNIVERSAL
Custom Provider
Connect another platform through the advanced universal integration editor.
- Webhook endpoint
- REST API configuration
- Authentication settings
- Verification policy
- Provider-specific mapping
The provider list is not the boundary of the platform.
Ready-made profiles save time. Custom Provider keeps the integration architecture open.
Explore Custom Provider →
Custom Provider
Your Platform Does Not Need an Evoxup Logo to Work With Evoxup.
When no ready-made provider profile exists, the universal integration editor provides the technical path for configuring a custom external platform.
Webhook URLAPI BaseAuthenticationVerification PolicyProduct IdentityHeaders
The purpose of Custom Provider is not to make every integration identical. It gives Evoxup a structured way to describe how that provider communicates, how events are verified and how external products are identified before fulfillment.
CUSTOM PROVIDER
Provider Slugmy-provider
Webhook TransportEnabled
API BaseConfigured
AuthenticationBearer / API Key
Verification PolicyProvider-specific
StatusACTIVE
Security & Verification
Use the Strongest Verification the Provider Actually Supports.
Security should increase trust without breaking legitimate commerce flows. Evoxup separates event transport, provider authentication, transaction verification and duplicate protection.
Signature Verification
Use provider signatures or HMAC where available.
Provider API Verification
Confirm the transaction against authoritative provider data before fulfillment when supported.
Credential Protection
Keep stored credentials out of ordinary editor output and expose replacement actions instead of plaintext values.
Duplicate Protection
Repeated events should not grant a second membership, license or fulfillment email.
Product Intelligence
Integrations Bring the Product In. Mapping and Sync Decide What Happens Next.
Provider connectivity is only the beginning. Evoxup separates external product discovery, internal routing and metadata synchronization.
D
Product Discovery
Provider APIs can expose external products so administrators can see what exists on the commerce platform.
M
Product Mapping
Map an external product identity to the correct EVO Product, Membership Plan or supported internal destination.
S
Product Sync
Refresh supported provider metadata such as name, status, price, purchase URL and variants without changing the internal business route.
Integration Capabilities
What Changes From Provider to Provider?
Not every provider offers the same APIs or security mechanisms. Evoxup keeps those differences explicit instead of hiding them behind inaccurate claims.
| Capability |
WooCommerce |
Gumroad Profile |
Lemon Squeezy Profile |
Custom Provider |
| WordPress-native commerce |
Yes | External | External | External / custom |
| Ready-made guided profile |
Native path | Yes | Yes | No — advanced editor |
| Webhook support |
Workflow-dependent | Yes | Yes | Configured by provider |
| Signature verification |
Depends on flow | Not required for provider ping model | Supported | Depends on provider |
| API verification |
Not the primary model | Supported | Supported workflow | Depends on API |
| Product discovery |
Internal products | Supported | Products / variants | Depends on provider API |
| Product Mapping |
Supported workflow | Supported | Supported | Supported where product identity is available |
| Product Sync |
Not required for native catalog | Supported | Supported | Depends on catalog API |
How an Integration Becomes Fulfillment
From External Event to Customer Access.
The integration layer does not grant access blindly. It passes the event through a defined lifecycle before fulfillment.
1
Receive
Accept the provider event or initiate the provider API flow.
2
Verify
Apply the provider's available signature, authentication or API verification method.
3
Normalize
Convert provider-specific data into a consistent internal event representation.
4
Identify & Map
Resolve the external product and map it to the intended EVO Product or plan.
5
Fulfill
Create the intended membership, license and entitlements according to product policy.
6
Record
Keep the result traceable and prevent duplicate fulfillment for the same transaction.
Why This Architecture Matters
Change the Store Without Rebuilding the Membership Platform.
A provider-neutral integration model gives you freedom to add, replace or combine commerce platforms while keeping Evoxup's internal product, membership and licensing architecture stable.
Reduce Provider Lock-In
Your membership rules stay inside Evoxup instead of being owned by one commerce provider.
Add Providers Gradually
Use ready-made profiles where they exist and Custom Provider for platforms that need a tailored configuration.
Keep Fulfillment Consistent
Different commerce sources can still lead into the same product, membership, license and entitlement lifecycle.
Universal Commerce for WordPress
Use the Provider You Want. Keep Evoxup at the Center.
Start with a ready-made provider profile or connect your own platform through the universal integration engine.
