Use Case 01: Marketplace intake API
Create sub-merchants during signup. Collect KYB data. Trigger underwriting. Sync verification status to your CRM through webhooks.
Pre-screening & VerificationIntegrate REST APIs and webhooks. Sync application status; receive dispute events.
Test risk, reserve and exception handling. Sandbox workspaces and test credentials are provisioned by our team under agreement.
Create sub-merchants during signup. Collect KYB data. Trigger underwriting. Sync verification status to your CRM through webhooks.
Pre-screening & VerificationReceive dispute and application-status events for your merchants.
EventsAPI access is issued under agreement to platform partners and integrated platforms. Talk to our team and we provision your sandbox workspace.
Your sandbox comes with test API keys and seeded test merchants, so you can build against realistic application, verification and settlement states.
The API is resource-oriented: applications, merchants, verifications and events. Create a test application and watch it move through Pre-screening and Verification.
We register your HTTPS endpoint with you and configure the events your workflow needs. Delivery, signatures and retries are covered below.
Authenticate with the API key issued to your workspace. Keys are environment-scoped — sandbox and production keys are separate — and are issued to you by our team.
Store keys in a secrets manager, never in source control.
Your systems should never poll for status. VeloSync pushes each state change to your endpoint as it happens — subscribe only to the families your workflow consumes.
Sub-merchant created, KYB submitted, verification approved or returned for more information.
Application created, stage changed, decision recorded.
Dispute opened, evidence requested, and final outcome — with the response deadline attached.
{
"id": "evt_9f2...",
"type": "application.status_changed",
"created": "2026-01-15T14:32:00Z",
"data": {
"application_id": "app_41c...",
"status": "verification"
}
}
Errors use standard HTTP status codes and a machine-readable error object with a stable code and a human-readable message.
400The request is malformed or fails validation.401 / 403The key is missing, invalid, or not scoped for this resource.404The resource does not exist in your workspace.409The resource is already in the requested state.429Rate limit reached; back off and retry.5xxOur side; safe to retry.All create calls accept an idempotency key, and retries should use exponential backoff with jitter.
Every webhook carries a signature. Verify it against your endpoint secret before processing; reject unsigned or mismatched deliveries.
Each event carries a unique event ID. Store it on first delivery and acknowledge duplicates without reprocessing.
If your endpoint is unavailable, delivery retries on an expanding schedule, and the event log keeps the full history available for replay.
Return a 2xx response as soon as an event is received, then process it asynchronously. Slow endpoints are treated as failed deliveries.
Test keys for every flow on this page. Trigger declines, disputes, reserve holds and failed transfers on demand; no real funds move.
We review your webhook handling, key storage and exception paths with you before production keys are issued.
Separate live keys, issued per environment. Rotate or revoke one key without touching the others; test and live data stay fully apart.
Build against the sandbox first — production will feel familiar.
Request Sandbox AccessService overviews as PDF downloads. Each document carries a watermark.
E-commerce infrastructure programs, the VeloCore™ console and continuous monitoring.
US enterprise landing services: modules, delivery and the service catalog.
Financing structures explained, and business banking, cards and payouts via partner institutions.