Fanbasis

Fanbasis is a creator-economy payments platform built for one-click checkout, recurring revenue, and creator storefronts. The Aura ↔ Fanbasis integration lets you attribute Fanbasis sales back to the Aura booking links and campaigns that drove them.

What you'll need

• A Fanbasis account with creator or admin permissions.
• Admin access to your Aura organization.
• ~2 minutes for the OAuth dance.

Setup

Step 1: Make sure Fanbasis is enabled for your account

Fanbasis is currently a gated integration. If you don't see it in your Aura Integrations list, contact support — we'll enable it on request.

Step 2: Open the integrations page

In Aura, go to Integrations → Fanbasis. (Or visit /integrations/fanbasis directly.)

Step 3: Click "Connect"

You'll be redirected to Fanbasis to authorize Aura. Fanbasis uses OAuth 2.0 with PKCE for the authorization flow — Aura never sees your Fanbasis password and stores nothing beyond the access token.

Step 4: Confirm in Fanbasis

Fanbasis shows a consent screen with the scopes Aura is requesting. Click Authorize. You're sent back to Aura.

Step 5: Verify the connection

You should see "Connected" with your Fanbasis account name. Connection complete.

What Phase 1 does today

• Identity sync: Aura knows which Fanbasis account you've connected.
• Token lifecycle: Aura refreshes your access token automatically before it expires. You shouldn't ever need to reconnect manually unless you revoke access on the Fanbasis side.
• OAuth introspection: Aura periodically validates that the token is still active (per RFC 7662) and disconnects gracefully if Fanbasis revokes it.

What Phase 1.5 will add (planned)

When Fanbasis publishes their product and order APIs:

• Product sync: Fanbasis products become selectable when you attach a product to an Aura booking link.
• Order attribution: Sales completed by leads who came through your Aura booking flows show up in your Analytics dashboard.
• Webhooks: payment.succeeded fires when an attributed Fanbasis order completes.

We'll notify connected Aura accounts when these land.

Token security

A few details for security-conscious admins:

• Aura's OAuth client_id and client_secret are server-only env vars. They never reach the browser.
• The OAuth state parameter (used to prevent CSRF) is AES-256-GCM encrypted with a 5-minute freshness window and silent secret-rotation support.
• Aura never asks for write access to your Fanbasis account. Read-only.
• You can revoke access at any time from Fanbasis itself — Aura honors the revocation immediately on the next API call.

Disconnecting

1. Integrations → Fanbasis.
2. Click Disconnect.

Disconnecting:

• Calls Fanbasis's revoke endpoint to invalidate the token there.
• Stops all sync activity in Aura.
• Preserves any data that was synced before disconnection.

You can reconnect later — your previous data won't be duplicated; it will pick up from where the sync left off.

Troubleshooting

"Authorization failed" after redirecting back from Fanbasis

Usually a clock-skew issue with the OAuth state validation — the encrypted state is valid for 5 minutes from the moment you click Connect. If you got distracted between clicking Connect and finishing the Fanbasis consent screen, just restart from Integrations → Fanbasis → Connect.

"Connection expired" banner

Fanbasis tokens have a built-in lifetime. Aura refreshes them in the background, but if the refresh token itself expires (or you revoked access on the Fanbasis side), you'll see this banner. Click Reconnect to redo the OAuth flow.

I don't see Fanbasis in my integrations list

The integration is gated. Contact support to have it enabled on your account.

Related

• Integrations overview
• Ablefy — analogous integration with a different checkout platform
• Settings → Products — where synced products will appear when Phase 1.5 lands