Crypto billing that feels like one payment method.

A customer accepts one clear billing agreement. Pulze then uses the safest permission their wallet supports to route scheduled payments within merchant, amount, frequency, and time limits.

Start now Merchant login Sweep dust

One agreement

Pulze asks for the fewest wallet approvals the customer’s wallet can safely support.

Guarded execution

Every charge stays inside live mandate, merchant, risk, and platform limits.

Human control

Customers can cancel; Pulze operations can pause a merchant, route, or payment rail.

setup.checklist

Create merchant account
Set payout wallet
Pick settlement stablecoin
Create payment link
Generate API key

POST /payment-links
mode: subscription
customer: connects wallet
settlement: USDC
approval: best supported flow
renewal: saved mandate

Public integration docs

The wallet stays in control. Pulze handles the payment work.

Compatible wallets can use delegated or batched permissions. Other wallets fall back to Permit2 or standard token approvals. The customer always sees and accepts the authority being granted; Pulze never treats a wallet connection as consent.

One understandable billing agreement

Network-specific permissions are managed progressively so future approved charges need the fewest confirmations possible without weakening revocation or platform controls.