canonical: https://jentic.com/apis/velopayments.com/velopayments # Velo Payments APIs Terms and Definitions Throughout this document and the Velo platform the following terms are used: * **Payor.** An entity (typically a corporation) which wishes to pay funds to one or more payees via a payout. * **Payee.** The recipient of funds paid out by a payor. * **Payment.** A single transfer of funds from a payor to a payee. * **Payout.** A batch of Payments, typically used by a payor to lo. The API exposes 109 endpoints secured with basic, oauth2 authentication. ## For AI agents Programmatically authentication endpoint, logout. Covers 109 operations with basic, oauth2 authentication. ## Scope Does not handle communications, crm, or developer tools - use for payments only. ## Capabilities - Authentication endpoint - Logout - Reset password - validate - List Users - Get User - Delete a User ## Use cases ### Payments Operations Use the Velo Payments APIs to perform payments operations programmatically. The API provides 109 endpoints covering core functionality including authentication endpoint, logout, reset password. Example prompt: Call POST `/v1/authenticate` to authentication endpoint ### Automated Payees Management Automate payees operations by combining multiple Velo Payments APIs endpoints. Agents can logout and then reset password in a single workflow. Example prompt: Call POST `/v1/logout` to logout, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Velo Payments APIs endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic, oauth2 tokens manually. Example prompt: Search Jentic for 'authentication endpoint', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/v1/authenticate` | Authentication endpoint | | POST | `/v1/logout` | Logout | | POST | `/v1/password/reset` | Reset password | | POST | `/v1/validate` | validate | | GET | `/v2/users` | List Users | | GET | `/v2/users/{userId}` | Get User | | DELETE | `/v2/users/{userId}` | Delete a User | | POST | `/v2/users/{userId}/disable` | Disable a User | ## Key resources - **Payees** — A payee is a person you wish to transfer money to. In this section you will find API opertions for w - **Payee Invitation** — Payee invitation is a process of inviting individual payees to the Velo platform. In this sction you - **Payors** — A Payor is the entity which is sending money. Here you will find the available APIs for working with - **Payor Hierarchy** —

Payors that are part of the same organization can be linked together in a hierarchical fashion

Payout APIs allow you to create and instruct payouts to payees

There are three phases to a ## Why Jentic - **Setup:** Wiring the Velo Payments APIs by hand means handling both basic auth and the OAuth2 client-credentials flow, choosing between the sandbox and production velopayments.com hosts, and coding each authentication and user operation yourself. Through Jentic you install once, import the Velo Payments APIs from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** Velo puts the user id in the URL path (`/v2/users/{userId}`), so a rule can pin your agent to one user. You choose the operations it may call, so destructive ones like deleting or disabling a user are not included unless you add them. - **Credential handling:** Your Velo Payments credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'authenticate a session' or 'list users', and Jentic returns the matching Velo Payments operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Stripe** — Alternative payments API - **Adyen** — Alternative payments API - **Square** — Complementary payments API - **Paypal** — Complementary payments API ## FAQ ### What authentication does the Velo Payments APIs use? The Velo Payments APIs uses basic, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I authentication endpoint with the Velo Payments APIs? Yes. Use the POST `/v1/authenticate` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Velo Payments APIs? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I authentication endpoint through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'authentication endpoint'. Jentic returns the matching Velo Payments APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Velo Payments APIs have? The Velo Payments APIs exposes 109 endpoints covering payees, payee invitation, payors operations. ### Can I limit what my agent is allowed to do with the Velo Payments API? Yes. Because you run Jentic One yourself, your own rules decide which Velo Payments operations and credentials your agent may use. Velo puts the user id in the URL path (`/v2/users/{userId}`), so you can pin the agent to a single user, and you pick the exact operations it may call. That means destructive calls such as deleting or disabling a user (DELETE `/v2/users/{userId}`, POST `/v2/users/{userId}/disable`) stay out of reach unless you explicitly include them.