About PopLayer

PopLayer is built for direct popunder deals that usually break down in the messy parts: stop events, partial delivery, payout arguments, invalid traffic, and leftover balances.

Why it exists

Most direct traffic deals work until something changes. A buyer pauses a campaign. A placement gets removed. Part of the traffic was good, part was not, and then settlement turns into chats, spreadsheets, and arguments.

PopLayer exists to make that money flow explicit. Accepted traffic gets paid. Invalid traffic never reaches settlement. If the deal stops, unused buyer funds return automatically instead of getting stuck in manual reconciliation.

What publishers get

Get paid immediately for accepted traffic

If a buyer stops, already accepted traffic still settles right away

Keep your current monetization while testing one placement

Set your own terms instead of relying only on network defaults

What buyers get

Accepted traffic only reaches settlement

Invalid traffic goes to fallback instead of becoming a later payout fight

Unused funds return automatically when a deal stops

Bring your own anti-fraud provider if you want stricter filtering

How PopLayer is different

Typical direct deal

  • • Traffic quality is argued about after the fact
  • • Payout logic lives in chats or manual spreadsheets
  • • Buyer stops can turn into payout disputes
  • • Leftover balances are reconciled manually

PopLayer

  • • Accepted traffic is explicit before settlement
  • • Invalid traffic falls out before payout
  • • Stop events trigger payout + refund logic automatically
  • • Every outcome stays visible in the audit trail

Why the system is built this way

The point is not to force blind trust in another ad network. Buyers can use the internal filter or bring their own anti-fraud provider. Publishers can test one placement without changing their whole stack.

Under the hood, PopLayer is built around stateful settlement logic, auditability, gasless daily operations, and payment flows that keep the messy cases from becoming payout chaos.

Infrastructure for messy deal states

The hard part is not launching a deal. The hard part is settling it fairly when traffic, quality, and timing are not perfectly clean.

Settlement logic
Accepted vs fallback flow
Invalid traffic never reaches settlement
Stop-event handling
Payout and refund split on pause, removal, or stop
Escrow-backed balance flow
Accepted traffic paid, unused funds returned
Verification
Internal anti-fraud engine
Built-in traffic validation before payout
BYOAF support
Buyers can connect their own anti-fraud provider
Auditable deal states
Clear trail for accepted, fallback, paid, and refunded amounts
Payment operations
Gasless daily usage
No native token setup for normal flows
Separate signers
Operational safety for exceptional actions
Stablecoin settlement
Direct payout flow designed for fast settlement
Analytics
Live traffic stats
Operational visibility while the deal is active
Event-level tracking
Data to understand why traffic was accepted or filtered
Audit logs
Shared record of what happened and why