Skip to main content
A policy is the financial rulebook for an AI session. It defines how much your AI can spend per day, how large any single transaction can be, at what amount a transaction requires your manual approval, which assets the AI is allowed to use, and how long a session created with this policy will remain active. Get your policies right before creating sessions — once a session is created, the policy attached to it is frozen in place.
If you’re setting up Pay3 for the first time, start with the CONSERVATIVE preset. You can always create a more permissive policy later once you’ve seen how your AI agent behaves.

​
Policy fields

allowedRecipientIds references contacts from your Contacts list. If this field is left empty, the AI can send to any valid Stellar address. If it is set, any payment to an address not on the list will be rejected.

​
Built-in presets

Pay3 ships with four presets. Choosing a preset automatically populates all numeric fields — you can then save it as-is or adjust individual values before saving.

​
Understanding the presets

BALANCED is a good fit for an AI assistant that handles a mix of small automated payments and occasional larger ones. The $250 threshold means the AI can execute most day-to-day transactions automatically while routing significant payments to you for review. The 7-day session duration reduces how often you need to reconfigure your client.
The DEFI preset is intended for AI agents running active DeFi strategies or high-frequency payment workflows. The higher limits and thresholds give the AI more autonomy. Only use this preset if you fully trust the AI agent’s logic and have reviewed its behavior in a lower-limit environment first.
Choose CUSTOM to set every field yourself. Use this when none of the presets match your workflow — for example, if you want a very long session duration with a low daily budget, or if you need to restrict the AI to a specific list of approved recipients.

​
Creating a policy

1

Open the Policies page

Click Policies in the dashboard navigation bar.
2

Enter a policy name

Type a descriptive name in the Name field. Choose something that makes the policy’s purpose obvious — you’ll see this name when selecting policies for sessions.
3

Select a preset

Choose one of the four presets from the Preset dropdown. If you choose CUSTOM, additional fields appear for you to fill in manually.
4

Save the policy

Click Create policy. The new policy appears in the policies list below the form, showing its name, preset type, daily budget, per-transaction max, approval threshold, and session duration.

​
Reusing policies across sessions

A single policy can be attached to multiple sessions. For example, you might create one “Standard” policy and use it for both your Cursor and Claude sessions. Changes you make to a policy after sessions are created do not propagate to those sessions — the session retains a snapshot of the policy as it existed at creation time.
If you need to change the spending rules for an active session, you must revoke the session and create a new one with the updated policy. There is no way to edit the policy parameters of an existing live session.