Introduction

Billing, payments, and margin intelligence for your business.

What is RevKeen?

RevKeen brings billing, payments, customer operations, and margin reporting together. Use the dashboard to run your business, or connect your own application through the API, SDKs, and webhooks.

Create products and subscriptions, collect payments, manage invoices, and understand how payment costs affect the revenue you keep.

What can you build?

How RevKeen fits your business

Your business holds its own payment-provider accounts. RevKeen supplies the software and orchestration around those relationships, including Elavon/NMI for card payments and London & Zurich for Direct Debit where configured.

RevKeen is not your merchant of record. Your business retains its customer, tax, and ordinary chargeback responsibilities. Platform fees and provider charges are separate; see Fees for the current pricing and scope.

Choose your starting point

If you are setting up your business, begin with account setup and provider onboarding. If you are building an integration, start with a staging key and a read-only API request.

Make your first staging request

Set your staging API key in your server environment, then list customers. A matching key returns 200 OK with a list payload.

Terminal · staging
export REVKEEN_API_KEY=rk_sandbox_your_api_key
curl https://staging-api.revkeen.com/v2/customers \
  -H "x-api-key: $REVKEEN_API_KEY" \
  -H "Accept: application/json"

Follow the complete quickstart · Authentication and key setup

Find your way around

Use the left menu to browse guides and reference pages. Search finds documentation and API operations. The On this page outline on the right shows your position within the current article; on smaller screens, open its page-outline menu.

The public RevKeen Assistant answers documentation questions. It has no access to your merchant account. For account-specific help, use Support.

Continue to Getting Started for the setup checklist. The Next and Previous links at the bottom of each page follow the documentation reading order.

On this page