Merchant Power User Guide

🎨 Branding & Appearance

Make the checkout experience your own. All settings are in the merchant portal under Settings:

⚙️ Payment Configuration

Control which payment methods your buyers can use and your cost structure:

• Payment platforms — Enable/disable specific payment methods. Only show what your customers actually use.

Venmo

CashApp

Zelle

Revolut

PayPal

Wise

Chime

Luxon Pay

Monzo

• Max spread — Set the maximum exchange rate spread you're willing to accept. This is the markup on the exchange rate that goes to liquidity providers. Lower spread = better rate for you, but may result in slower order fulfillment. Higher spread = faster fills, higher cost.
• Default currency — Choose the base currency for your orders.

📊 How Tranche Tiers Work

Peer Pay supports tiered spread caps based on order size. This means you can set different maximum spreads for different transaction amounts — so larger orders get better rates automatically.

The idea is simple: you decide which order sizes matter most to your business and set your willingness to pay accordingly.

• If there are certain order sizes you really want access to, you can set a higher spread cap for those tiers — signaling to LPs that you're willing to pay a premium for fast fills at that size
• For order sizes you care less about, set a lower cap — you won't overpay on transactions that aren't as valuable to you
• Market rates move constantly, so there's no universal "right" spread — it depends on your business, your volume, and what you're optimizing for

🔧 Setting Up Your Tranches

Tranche configuration is available in your merchant settings. Define your tiers based on your business needs:

• Set the order size breakpoints that match your typical transaction sizes
• Assign a max spread cap for each tier — higher for sizes you want prioritized, lower for sizes you're less willing to pay for
• The system automatically applies the correct tier based on order amount
• Buyers always see the final price — they don't see the spread breakdown
• Adjust anytime as market conditions and your needs change

In this setup, the merchant is willing to pay a higher premium on small orders to ensure they fill quickly — that's where their volume is. Larger orders get a tighter cap since they're less frequent. Your configuration will look completely different depending on your business — this is just one example. Set each tier based on what you prioritize.

🌉 Receive Any Token on Any Chain

By default, Peer Pay settles in USDC on Base. But with auto-bridging, you can configure your checkout to automatically bridge and convert funds so you receive a specific token on a specific chain.

• Buyer pays in fiat (Venmo, CashApp, etc.) → order completes → funds are automatically bridged to your target chain and swapped to your target token
• No manual bridging or swapping required on your end
• Settlement happens automatically after order completion

⛓️ Supported Chains & Use Cases

Auto-bridging supports major EVM chains and tokens. Common configurations:

📤 Forward Funds to a Custom Wallet

By default, completed orders deposit USDC into your merchant wallet. With order forwarding, you can route funds directly to a different wallet address instead.

• Deposit address — Perfect for casinos, poker platforms, and onramps: generate a unique deposit address and have funds land directly into a player's account or platform wallet. No manual transfers needed.
• Treasury wallet — Send directly to your company's multisig or treasury
• Smart contract — Route funds into a DeFi protocol, vault, or staking contract automatically
• Cold storage — Forward to a hardware wallet address for maximum security
• Third-party — Pay suppliers, partners, or service providers directly from order revenue

🔄 Forwarding + Auto-Bridging

These features stack. You can configure your checkout to:

1. Accept fiat payment from the buyer
2. Auto-bridge to your target chain and token
3. Forward the resulting tokens to a custom wallet address

Example: Buyer pays $500 via Venmo → auto-bridges to ETH on Arbitrum → deposits directly into your Arbitrum treasury wallet. Fully automated, no manual steps.

🤝 Revenue Sharing

Peer Pay supports referral-based fee splitting — a way to share revenue with partners, affiliates, or platforms that drive volume to your checkout.

• Referral fees — Set a percentage of transaction value to be automatically split with a referrer
• Affiliate tracking — Generate unique referral links to track which partner drove each transaction
• Automatic payouts — Revenue share is calculated and allocated automatically per transaction

📐 Fee Structure Breakdown

Here's how fees layer in a typical Peer Pay transaction:

All fees are transparent and configurable. The buyer sees one final price — they don't see the breakdown between platform, spread, merchant, and referral fees.

🧩 Embed Peer Pay on Any Website

Peer Pay is not limited to Telegram. The Telegram bot is just one way to create orders — the checkout SDK lets you integrate Peer Pay directly into literally any website or app. No Telegram account required.

• Embedded checkout — iFrame or redirect-based integration, works on any website
• Customizable UI — Match your brand's look and feel (or go fully white-label)
• Webhooks — Get real-time notifications when orders are created, completed, or expired
• Programmatic order creation — Create orders via API — no Telegram, no manual steps
• No Telegram dependency — The SDK is a standalone integration. Use it without ever touching the Telegram bot

👻 White-Label / Hide Peer Branding

For merchants who want a fully branded experience, Peer Pay supports white-label mode — removing Peer branding entirely from the checkout flow.

• Hide "Powered by Peer" — Remove all Peer logos and branding from the checkout page
• Custom domain — Serve the checkout from your own domain for a seamless experience
• Full brand control — Your name, your colors, your logo — buyers never see Peer

🔔 Webhooks

Webhooks are configured in your merchant portal. They send real-time HTTP callbacks to your server when order events occur:

• order.created — Buyer initiated an order
• order.completed — Payment verified, USDC settled
• order.expired — 4-hour window elapsed without completion
• order.cancelled — Order was cancelled

Set your webhook URL in the merchant portal under Settings. Webhooks let you automate downstream actions — update your database, send confirmation emails, trigger fulfillment, or credit user accounts automatically. For full webhook payload reference, see docs.peer.xyz.

📈 Scaling Your Volume

• Start small, scale up — Run test orders first, then gradually increase ticket sizes
• Monitor fill times — If orders take too long to fill, consider increasing your max spread slightly to attract more LP liquidity
• Peak hours — Liquidity is generally higher during US business hours (9am–9pm ET). Plan larger orders accordingly
• Spread your orders — Instead of one $5,000 order, consider splitting into multiple smaller orders for faster fills (unless using tranche tiers with favorable large-order rates)

🛡️ Chargeback Prevention

Chargebacks are your responsibility. Here's how to minimize risk:

• Vet your buyers — Know who you're transacting with, especially for large amounts
• Start with small orders — Build trust before processing large transactions with new buyers
• Keep records — Save order IDs, timestamps, and communication logs
• Set expectations — Make sure buyers understand the payment is final
• Monitor patterns — Repeated small orders from unknown buyers can be a red flag

👥 Team Management

For businesses with multiple team members handling payments:

• Invite team members via the merchant portal using email invite links
• Each team member gets their own access to view orders and manage settings
• Coming soon: Team members will be able to send out payment links on behalf of your merchant account

🧪 Sandbox & Testing

Before going live with a full integration, we recommend testing in a sandbox environment:

• Test orders — Create small test orders to validate your setup, webhooks, and forwarding configuration
• SDK sandbox — Test your embedded checkout integration without processing real payments
• Webhook testing — Verify your server correctly receives and handles webhook payloads before going live
• End-to-end validation — Walk through the complete flow: order creation → buyer payment → settlement → forwarding/bridging