Back to Dashboard
Payment Credentials Setup
Follow the steps below to get your API credentials from each payment platform and enter them in VaultReader. All credentials are encrypted with AES-256-GCM before storage.
Gumroad
VaultReader verifies purchases by checking your Gumroad sales using your access token. Official Gumroad API docs
- Log in to app.gumroad.com
- Click your profile icon (top right) → Settings
- Click the Advanced tab in the left sidebar
- Scroll down to API → Click "Create application"
- Give it any name (e.g. "VaultReader") and click Create
- Once created, you'll see your Access Token on the application page
- Copy the access token immediately
Important: You must create an application first before you can generate an access token. Copy the token immediately — Gumroad will only show it once. Paste it into the Access Token field in VaultReader Settings → Payment Credentials.
What it looks like: A long string of letters and numbers (e.g.
8wJgo4wjPZQ-sZokbSImWU3nAZmGoy4VJGc0dMQH4Pk). This is your access token, NOT a license key.
Stripe
VaultReader uses your Stripe Secret Key to verify payments via the Stripe API.
- Log in to dashboard.stripe.com
- In the left sidebar, click Developers → API keys
- You'll see your Publishable key and Secret key
- Click "Reveal live key" next to the Secret key (or use test key for testing)
- Copy the full secret key
Important: Use the Secret key (starts with
sk_live_ for production or sk_test_ for testing). Do NOT use the Publishable key (pk_).
Test mode: Use
sk_test_ keys during development. Switch to sk_live_ keys when you go live. VaultReader will respect both.
Paddle
VaultReader uses your Paddle Vendor ID and Auth Code to verify purchases.
- Log in to sandbox-vendors.paddle.com (sandbox) or vendors.paddle.com (production)
- Click Developer Tools in the left sidebar
- Click Authentication
- Your Vendor ID is displayed at the top of the page
- Click "Generate" next to Auth Code (or copy your existing one)
Important: You need both the Vendor ID (a number like
12345) and the Auth Code (a long string). Copy the Auth Code immediately — it may only be shown once.
Sandbox vs Production: Use sandbox credentials (
sandbox-vendors.paddle.com) for testing, production credentials for live sales.
PayPal
VaultReader uses PayPal REST API credentials to verify purchases.
- Log in to developer.paypal.com
- Click My Apps & Credentials in the dashboard
- Scroll to REST API apps
- Click Create App (or select an existing app)
- Under the Live (or Sandbox) tab, you'll see Client ID and Secret
- Copy both values
Important: You need both the Client ID and the Secret. Click "Show" next to the Secret to reveal it. Use Live credentials for production, Sandbox for testing.
App not created? If you don't have a REST API app yet, click "Create App" and give it any name (e.g. "VaultReader"). You'll get a Client ID and Secret immediately.
LemonSqueezy
VaultReader uses your LemonSqueezy API key to verify purchases.
- Log in to app.lemonsqueezy.com
- Click Settings in the left sidebar
- Click the API tab
- Scroll to API Keys
- Click "Create API Key" (or copy an existing one)
- Give it any name (e.g. "VaultReader") and click Create
Important: Copy the API key immediately — LemonSqueezy will only show it once. Paste it into the API Key field in VaultReader Settings.
Permissions: The API key needs at minimum "Products" and "Orders" read access to verify purchases. Default permissions are usually sufficient.