Paddle Wrapper

Paddle is the leading Merchant of Record for digital product companies. It handles payments, subscriptions, tax, compliance, and fraud for more than 6,000 SaaS, AI, and app companies worldwide, replacing the need for a complex, fragmented payment stack.

The Paddle Wrapper brings your billing data into Postgres as queryable foreign tables. Query and write products, customers, subscriptions, transactions, and more with plain SQL and join them against your application data. The wrapper works with Supabase Vault for secure API key management and is built on WebAssembly (Wasm) for lightweight, sandboxed execution.

Supported Operations

Object	Select	Insert	Update	Delete
Products	✅	✅	✅
Prices	✅	✅	✅
Discounts	✅	✅	✅
Customers	✅	✅	✅
Transactions	✅	✅	✅
Reports	✅
Notification Settings	✅	✅	✅
Notifications	✅

Preparation

Before you get started, make sure the wrappers extension is installed on your database:

and then enable the Wasm foreign data wrapper:

Secure your credentials (optional)

By default, Postgres stores FDW credentials inside pg_catalog.pg_foreign_server in plain text. Anyone with access to this table will be able to view these credentials. Wrappers is designed to work with Vault, which provides an additional level of security for storing credentials. We recommend using Vault to store your credentials.

Connecting to Paddle

We need to provide Postgres with the credentials to access Paddle, and any additional options. We can do this using the create server command:

With Vault:

Without Vault:

Note: the fdw_package_* options are required and specify the Wasm package metadata. See the Available Versions table above for the full list.

Resources

• Official supabase/wrappers documentation: Paddle
• Enable in Supabase dashboard
• supabase/wrappers on GitHub
• Paddle API documentation
• Paddle product page