velopayments.com
Velo Payments provides a business payments platform for organizations to onboard payees, fund accounts, and send and track payouts. It offers sandbox and production environments for integrating payment workflows.
Velo Payments exposes a documented REST API for payor, payee, payout, funding, webhook, auth, and reporting operations; no public GraphQL, MCP server, or CLI surfaces were found.
- Velo Payments APIsdiscovered
Request Sandbox or production access from Velo Development Center. Velo backoffice staff add your organization as a payor, then create and securely share your payor ID, API key, and API secret. Use the API key and API secret together as HTTP Basic credentials to call POST /v1/authenticate?grant_type=client_credentials and obtain a bearer access token for API calls.
First obtain your Velo-issued API key and API secret from Velo Development Center. Base64-encode `<api_key>:<api_secret> and send it in the Authorization: Basic ... header to POST https://api.sandbox.velopayments.com/v1/authenticate?grant_type=client_credentials (or the production host) as documented in [Velo API docs](https://apidocs.velopayments.com/). The response returns an access_token; send that token as Authorization: Bearer <access_token>` on subsequent API requests.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing