Developers

Build payments into your product. Track every result.

Create payments with our REST API, connect them to your orders and receive status updates through signed webhooks. Build with test keys before requesting production access.

Create an account to test the API Dashboard documentation

Developers working together in a bright studio

API

Payments, connected to your tools.

Create payments, receive events and reconcile orders.

POST /v1/paylinks

curl -X POST https://api.zyndpay.io/v1/paylinks \
  -H 'Authorization: Bearer YOUR_TEST_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "slug": "order-1042",
    "title": "Order 1042",
    "amountMinor": 12000000,
    "currency": "USDT",
    "acceptedMethods": ["CRYPTO"],
    "category": "SERVICE_ONLINE"
  }'

Test example for a completed business profile. Use your test key, a unique slug and an enabled currency and payment method. See the API reference before integrating.

Developers

From test keys to a connected checkout.

1 · Set up test access

Create a business account and open the developer tools in your dashboard. Generate a test API key and keep it on your server.

2 · Create a payment link

Send a request to POST /v1/paylinks with your test key and the required payment details. Use the returned link to test the hosted customer journey.

3 · Handle payment events

Configure your webhook endpoint and verify the signature on each delivery. Use the payment status and your order reference to update your application.

Keep your system in sync.

Verify signed deliveries using the documented timestamp and raw-body format.
Automatic retries help recover from temporary delivery failures.
Inspect delivery history and replay supported events from the dashboard.
Build an idempotent handler so duplicate deliveries do not repeat an action.

Test before you launch.

Use a zynd_test_* key to exercise supported test flows without production funds. Complete business verification and review enabled payment methods before switching to live processing.

Control integration access.

Separate test and live credentials, assign the permissions your integration needs and rotate API keys from the dashboard.

Dashboard documentation

Integration resources

Build the right checks into your flow.

Use these public starting points alongside the account-specific developer documentation. Enabled capabilities and live access remain account-scoped.

Let’s discuss your next step.