Developers

Documentation

Integrate REST APIs and webhooks. Sync application status; receive dispute events.

Build before you go live

Sandbox ready

Test risk, reserve and exception handling. Sandbox workspaces and test credentials are provisioned by our team under agreement.

Request Sandbox Access
Core flows

From signup to institutional review.

01

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 & Verification
02

Use Case 02: Vertical SaaS — status and dispute events

Receive dispute and application-status events for your merchants.

Events

Getting started

  1. 1

    Request access

    API access is issued under agreement to platform partners and integrated platforms. Talk to our team and we provision your sandbox workspace.

  2. 2

    Get your sandbox keys

    Your sandbox comes with test API keys and seeded test merchants, so you can build against realistic application, verification and settlement states.

  3. 3

    Make your first call

    The API is resource-oriented: applications, merchants, verifications and events. Create a test application and watch it move through Pre-screening and Verification.

  4. 4

    Configure webhooks

    We register your HTTPS endpoint with you and configure the events your workflow needs. Delivery, signatures and retries are covered below.

Authentication

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.

  • Key rotation is arranged with our team, with an overlap window so live integrations keep working during the switch.
  • Optional IP allowlisting restricts a key to your servers. All traffic runs over TLS 1.2 or higher.
Webhooks

Every state change, delivered as an event.

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.

1

Pre-screening & Verification

Sub-merchant created, KYB submitted, verification approved or returned for more information.

2

Application status

Application created, stage changed, decision recorded.

3

Disputes

Dispute opened, evidence requested, and final outcome — with the response deadline attached.

Example event payload
{
  "id": "evt_9f2...",
  "type": "application.status_changed",
  "created": "2026-01-15T14:32:00Z",
  "data": {
    "application_id": "app_41c...",
    "status": "verification"
  }
}

Errors & retries

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.

Delivery & security

Built for retries, duplicates and downtime.

Signed deliveries

Every webhook carries a signature. Verify it against your endpoint secret before processing; reject unsigned or mismatched deliveries.

Idempotent by design

Each event carries a unique event ID. Store it on first delivery and acknowledge duplicates without reprocessing.

Automatic retries

If your endpoint is unavailable, delivery retries on an expanding schedule, and the event log keeps the full history available for replay.

Acknowledge fast

Return a 2xx response as soon as an event is received, then process it asynchronously. Slow endpoints are treated as failed deliveries.

Sandbox to production

One integration path, two key sets.

1

Sandbox keys

Test keys for every flow on this page. Trigger declines, disputes, reserve holds and failed transfers on demand; no real funds move.

2

Go-live review

We review your webhook handling, key storage and exception paths with you before production keys are issued.

3

Production keys

Separate live keys, issued per environment. Rotate or revoke one key without touching the others; test and live data stay fully apart.

Go-live checklist

  • Program verification complete for your organization
  • Webhook endpoint live, signature verification enabled
  • Test events received end-to-end in the sandbox
  • Production keys issued and stored in your secrets manager
  • Settlement account confirmed with your acquiring partner

Build against the sandbox first — production will feel familiar.

Request Sandbox Access

Product & Service Documents

Service overviews as PDF downloads. Each document carries a watermark.

E-commerce Infrastructure & VeloCore™ — Overview

E-commerce infrastructure programs, the VeloCore™ console and continuous monitoring.

Download PDF

Setup & Support — Service Overview

US enterprise landing services: modules, delivery and the service catalog.

Download PDF

Financing & Banking — Overview

Financing structures explained, and business banking, cards and payouts via partner institutions.

Download PDF