Policies

Policies are the rules PMP applies inside a program.

A policy can use approved onchain state, business data, customer status, or external inputs. The rule set determines who qualifies, what USDv exposure counts, how rewards are calculated, and where settlement goes.

Eligibility policies

Eligibility policies define who or what qualifies.

Examples:

• KYC-approved customers only
• minimum balance required
• supported jurisdictions only
• specific customer tiers
• allowlists
• denylists
• account status requirements

Trigger policies

Trigger policies define events or external inputs that activate a rule.

A trigger can come from onchain activity, offchain business data, or an approved external data source.

Examples of onchain triggers

• customer provides liquidity to an approved pool
• customer holds USDv in a specific smart contract
• customer uses USDv as collateral in an approved market
• customer reaches a volume threshold onchain
• customer interacts with a specific Solana program
• customer swaps for a specific token

Examples of offchain triggers

• customer completes onboarding
• customer reaches a card spend threshold
• customer is assigned to a partner campaign
• customer belongs to a specific product tier
• customer completes an action tracked by the business

Examples of external data inputs

• approved partner attribution data
• liquidity or market data
• account status
• campaign qualification data
• oracle-fed market information

Trigger policies make Programs more flexible. They let a business tie USDv economics to behavior inside its product, not just to passive balances.

Allocation policies

Allocation policies define how much value is assigned.

Examples:

• base reward allocation
• boosted allocation for a campaign
• higher allocation after a trigger event
• higher allocation for a customer tier
• higher allocation for a partner segment

Split policies

Split policies define who receives what share.

Examples:

• 100% to customers
• 100% to the business
• 80% to customers and 20% to the business
• 70% to customers, 20% to the business, 10% to a partner

Routing policies

Routing policies define where rewards go.

Examples:

• customer wallet
• app account
• business treasury
• rewards wallet
• partner wallet
• campaign wallet

Schedule policies

Schedule policies define when rewards settle.

Examples:

• weekly
• biweekly
• monthly
• at the end of a campaign
• after a trigger event is verified

Tranche policies

Tranche policies define tiered treatment.

Examples:

• balances above 1,000 USDv receive a higher allocation
• balances above 10,000 USDv receive a higher allocation
• customers in a higher product tier receive a higher allocation
• balances held for longer receive a higher allocation
• customers who complete a trigger event move into a higher tier

One-time policies

One-time policies define event-based rewards.

Examples:

• first deposit
• first card transaction
• account activation
• campaign completion
• minimum balance reached
• first liquidity provision to an approved market