user_id. To fund cards yourself, use the company wallet instead.
kyc_required. The response then carries a checkout_url. Send it to the user: Agentcard covers the provider fee, so send the exact amount the user should receive. Learn when the money lands from a fresh read of the funding session.
The first funding needs a verified phone. Without one, the request is refused:
checkout_url is null, and the phone code is always 111111.
Cap what leaves a user’s balance
Spend limits are not open to every company yet. Until yours reaches them, all three requests answer:$250 under a $100 daily limit can spend $100 today and the rest over the next days.
The per-transaction limit is also held by the wallet provider that keeps the user’s balance, which refuses a larger transfer on its own. The daily and monthly limits are held by Agentcard alone, since the wallet provider judges one transfer at a time. Read wallet_provider_policy.status in the response to see whether the provider holds yours yet. Until it does, Agentcard never moves more in one transfer than the provider still allows, and retries every few minutes.
The limits sit on the user’s balance, which is shared by every company the user is connected to. When two companies set limits on the same user, the user’s balance obeys the smaller figure of each limit. Each company reads back only its own figures, and stricter_limit_applies tells it whether a smaller one from elsewhere holds. Your limits are removed when the user disconnects from your company.