Advanced configuration, fee optimization, cross-chain settlement, and everything you need to run Peer Pay at scale.
← Basic Setup GuideMake the checkout experience your own. All settings are in the merchant portal under Settings:
Displayed to buyers on the checkout page. Use your brand name, not a personal name.
Customize the checkout accent color to match your brand. Applies to buttons, highlights, and UI elements.
Upload your logo. Shown on the checkout page so buyers know who they're paying.
Set the default fiat currency for your checkout. Buyers see prices in your chosen currency.
Control which payment methods your buyers can use and your cost structure:









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.
Tranche configuration is available in your merchant settings. Define your tiers based on your business needs:
| Order Size | Max Spread Cap |
|---|---|
| $0 – $499 | 8% |
| $500 – $999 | 6% |
| $1,000 – $1,499 | 5% |
| $1,500 – $2,499 | 4.5% |
| $2,500+ | 4% |
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.
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.
Auto-bridging supports major EVM chains and tokens. Common configurations:
| Use Case | Receive | Chain |
|---|---|---|
| Default (no bridging) | USDC | Base |
| Ethereum mainnet settlement | USDC / ETH | Ethereum |
| Arbitrum DeFi | USDC / ARB | Arbitrum |
| Polygon operations | USDC / MATIC | Polygon |
| Custom token | Any supported ERC-20 | Any supported chain |
By default, completed orders deposit USDC into your merchant wallet. With order forwarding, you can route funds directly to a different wallet address instead.
These features stack. You can configure your checkout to:
Example: Buyer pays $500 via Venmo → auto-bridges to ETH on Arbitrum → deposits directly into your Arbitrum treasury wallet. Fully automated, no manual steps.
Peer Pay supports referral-based fee splitting — a way to share revenue with partners, affiliates, or platforms that drive volume to your checkout.
Here's how fees layer in a typical Peer Pay transaction:
| Fee Layer | Who Sets It | Who Receives It |
|---|---|---|
| Platform fee | Peer (automatic) | Peer |
| Spread | Market / LP | Liquidity providers |
| Merchant fee | You (configurable) | You |
| Referral fee | You (configurable) | Your referral partner |
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.
Chargebacks are your responsibility. Here's how to minimize risk:
For businesses with multiple team members handling payments:
Test your full integration before going live:
It depends on your priority. Lower spread = cheaper for you, but orders may take longer to fill because fewer LPs are willing to provide liquidity at thin margins. Higher spread = faster fills, higher cost. Start with the default and adjust based on fill speed. If you're processing time-sensitive payments, err on the higher side.
Yes. Tranche adjustments take effect on new orders. Existing live orders keep the spread they were created with.
The order stays open until an LP fills it or the 4-hour timer expires. If your spread cap is too low for the order size, LPs may not find it profitable enough to fill. Consider raising your max spread or breaking the order into smaller amounts.
Bridge fees are minimal (usually under $1) and are factored into the final order cost. The convenience of receiving funds on your target chain without manual bridging typically far outweighs the small bridge fee.
Yes, as long as the smart contract can receive ERC-20 tokens. Make sure it has the appropriate receive/fallback functions. Test with a small amount first.
If a bridge transaction fails, the USDC remains in your merchant wallet on Base as a fallback. No funds are lost. Contact us if you see a stuck bridge transaction.
Yes. The SDK and Telegram bot are independent. You can use either or both. The SDK is ideal for website integrations where you want an embedded checkout experience.
Yes. In the merchant portal, click Sandbox in the sidebar to enable sandbox mode. You will get a separate sandbox merchant ID and API key for testing your integration without processing real payments.
Yes. White-label mode lets you remove all Peer branding so the checkout looks entirely like your own product. Ideal for platforms and aggregators. Configure in your merchant portal.
Webhooks are configured in the merchant portal under Settings. Add your endpoint URL and select which events to subscribe to. For payload format and technical details, see docs.peer.xyz.
Full developer documentation including SDK setup, API reference, webhook payloads, and code examples are at docs.peer.xyz under the "Integrate Peer" section.
Your buyers need this to complete payments. You need it to offramp for free.