@kelviq/mcp-server 1.2.1 → 1.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +40 -3
- package/dist/config.d.ts +5 -0
- package/dist/config.js +1 -0
- package/dist/config.js.map +1 -1
- package/dist/docs/ai/docs-for-agents.md +21 -0
- package/dist/docs/ai/overview.md +43 -0
- package/dist/docs/api-reference/authentication.md +9 -3
- package/dist/docs/api-reference/introduction.md +23 -2
- package/dist/docs/backend-integration/node-sdk.md +12 -6
- package/dist/docs/backend-integration/python-sdk.md +14 -8
- package/dist/docs/changelog.md +352 -3
- package/dist/docs/checkout/checkout-configuration.md +25 -75
- package/dist/docs/checkout/checkout-design.md +76 -0
- package/dist/docs/checkout/checkout-examples.md +212 -0
- package/dist/docs/checkout/checkout-metadata.md +1 -1
- package/dist/docs/checkout/custom-fields.md +60 -0
- package/dist/docs/checkout/embed-checkout.md +280 -0
- package/dist/docs/checkout/payment-methods/upi.md +69 -0
- package/dist/docs/checkout/payment-methods.md +119 -0
- package/dist/docs/checkout/static-checkout-url.md +3 -2
- package/dist/docs/cli/commands.md +57 -4
- package/dist/docs/cli/kelviq-config.md +1 -1
- package/dist/docs/cli/overview.md +1 -0
- package/dist/docs/customer-portal/managing-payment-methods.md +4 -4
- package/dist/docs/customer-portal/overview.md +7 -7
- package/dist/docs/customer-portal/retention.md +109 -0
- package/dist/docs/customers-management/overview.md +105 -0
- package/dist/docs/frontend-integration/js-sdk.md +11 -11
- package/dist/docs/frontend-integration/promotions-ui-js.md +2 -2
- package/dist/docs/frontend-integration/react-sdk.md +8 -49
- package/dist/docs/frontend-integration/react-ui.md +8 -6
- package/dist/docs/getstarted/fees.md +27 -11
- package/dist/docs/getstarted/introduction-to-kelviq.md +29 -66
- package/dist/docs/getstarted/merchant-of-record.md +18 -24
- package/dist/docs/getstarted/overview.md +98 -0
- package/dist/docs/getstarted/review-process.md +59 -59
- package/dist/docs/guides/agent-toolkit.md +14 -9
- package/dist/docs/guides/mcp-server.md +24 -9
- package/dist/docs/guides/migrate-from-lemon-squeezy.md +405 -0
- package/dist/docs/guides/sandbox.md +6 -4
- package/dist/docs/guides/set-up-with-ai.md +43 -0
- package/dist/docs/guides/subscription-integration-for-nextjs.md +10 -11
- package/dist/docs/guides/subscription-integration.md +1 -1
- package/dist/docs/guides/test-payments.md +640 -0
- package/dist/docs/guides/webhooks.md +182 -30
- package/dist/docs/integrations/woocommerce.md +88 -0
- package/dist/docs/integrations/zapier.md +22 -0
- package/dist/docs/legal/account-and-funds.md +59 -0
- package/dist/docs/legal/approved-prohibited-policy.md +32 -27
- package/dist/docs/legal/payment-flow-diagram.md +7 -7
- package/dist/docs/manifest.json +160 -41
- package/dist/docs/openapi.json +1359 -109
- package/dist/docs/payouts/overview.md +14 -12
- package/dist/docs/payouts/payout-account.md +1 -1
- package/dist/docs/payouts/transactions.md +3 -3
- package/dist/docs/product-catalog/create-a-feature.md +3 -3
- package/dist/docs/product-catalog/digital-downloads.md +5 -5
- package/dist/docs/product-catalog/discounts.md +2 -2
- package/dist/docs/product-catalog/entitlements.md +20 -27
- package/dist/docs/product-catalog/free-and-trials.md +4 -4
- package/dist/docs/product-catalog/license-keys.md +56 -29
- package/dist/docs/product-catalog/links.md +3 -3
- package/dist/docs/product-catalog/location-based-pricing.md +6 -10
- package/dist/docs/product-catalog/one-time-payments.md +3 -7
- package/dist/docs/product-catalog/pay-as-you-go.md +8 -8
- package/dist/docs/product-catalog/plans.md +22 -19
- package/dist/docs/product-catalog/products.md +11 -3
- package/dist/docs/product-catalog/proration.md +69 -0
- package/dist/docs/product-catalog/seat-based-pricing.md +7 -7
- package/dist/docs/product-catalog/subscriptions.md +52 -22
- package/dist/docs/product-catalog/tax-settings.md +8 -8
- package/dist/docs/product-catalog/usage-alerts.md +7 -7
- package/dist/docs/product-catalog/usage-based-billing.md +156 -29
- package/dist/docs/product-catalog/usage-limits.md +78 -0
- package/dist/docs/promotions/create-a-promotion.md +2 -2
- package/dist/docs/promotions/overview.md +1 -1
- package/dist/docs/quickstart/core-concepts.md +36 -30
- package/dist/docs/quickstart/dashboard-setup.md +26 -22
- package/dist/docs/quickstart/integrate-with-your-app.md +133 -52
- package/dist/docs/sales/abandoned-cart-recovery.md +7 -3
- package/dist/docs/sales/checkout-sessions.md +28 -39
- package/dist/docs/sales/orders.md +30 -54
- package/dist/docs/settings/customer-emails.md +52 -0
- package/dist/docs/settings/members.md +27 -0
- package/dist/docs/settings/profile.md +26 -0
- package/dist/docs/settings/zapier.md +22 -0
- package/dist/http/errors.d.ts +20 -1
- package/dist/http/errors.js +83 -31
- package/dist/http/errors.js.map +1 -1
- package/dist/schemas/kelviq.d.ts +54 -0
- package/dist/schemas/kelviq.js +64 -0
- package/dist/schemas/kelviq.js.map +1 -1
- package/dist/server.js +3 -2
- package/dist/server.js.map +1 -1
- package/dist/tools/imports.d.ts +68 -0
- package/dist/tools/imports.js +242 -0
- package/dist/tools/imports.js.map +1 -0
- package/dist/tools/index.d.ts +2 -1
- package/dist/tools/index.js +4 -1
- package/dist/tools/index.js.map +1 -1
- package/package.json +1 -1
|
@@ -12,7 +12,7 @@ Kelviq can push event notifications to your server whenever something meaningful
|
|
|
12
12
|
|
|
13
13
|
When an event occurs, Kelviq creates a `WebhookEvent` and fans it out to all enabled endpoints you have registered for that event type. Each delivery is a single `POST` request with a JSON body and signed headers.
|
|
14
14
|
|
|
15
|
-
Kelviq retries
|
|
15
|
+
A delivery is considered successful when your endpoint returns a `2xx` status code. Kelviq retries a delivery up to **3 times**, with a 60-second delay between attempts, when the request fails to connect, times out after 10 seconds, or your endpoint returns a `5xx` status code or `429 Too Many Requests`. Other `4xx` and `3xx` responses are not retried; Kelviq does not follow redirects.
|
|
16
16
|
|
|
17
17
|
---
|
|
18
18
|
|
|
@@ -20,18 +20,51 @@ Kelviq retries failed deliveries up to **3 times** with a 60-second delay betwee
|
|
|
20
20
|
|
|
21
21
|
Go to **Settings → Webhooks** in the [Kelviq dashboard](https://app.kelviq.com/settings/webhooks/new) to create a webhook endpoint. You will specify:
|
|
22
22
|
|
|
23
|
-
- **URL** — The public HTTPS URL Kelviq will POST events to.
|
|
24
|
-
- **Events** — The subset of event types you want to subscribe to.
|
|
23
|
+
- **URL** — The public HTTPS URL Kelviq will POST events to. A URL that points to a private or internal address is rejected.
|
|
24
|
+
- **Events** — The subset of event types you want to subscribe to; at least one is required. The **Sample payload** panel shows the shape of any event before you subscribe.
|
|
25
|
+
- **Name** *(optional)* — How the endpoint appears in the dashboard. It defaults to the URL's host, for example `api.acmecorp.com`.
|
|
26
|
+
- **Description** *(optional)* — A note for your team.
|
|
25
27
|
|
|
26
28
|
After creation, Kelviq generates a signing secret for the endpoint in the format `kq_whsec_<random>`. Store this secret securely — you will need it to verify signatures.
|
|
27
29
|
|
|
28
|
-
|
|
30
|
+
Treat your signing secret like a password: anyone who has it can forge deliveries. You can read it from the endpoint at any time, and regenerate it from the endpoint's settings if it leaks. Update your server first when you do: deliveries already in flight were signed with the old secret.
|
|
31
|
+
|
|
32
|
+
The same endpoints are available over the API with a server key: see [Webhook Endpoints](/api-reference/webhook-endpoints/list-webhook-endpoints).
|
|
33
|
+
|
|
34
|
+
### Verify your endpoint
|
|
35
|
+
|
|
36
|
+
**Verify endpoint**, on the form and on the endpoint page, sends one empty `POST` to your URL with no event and no signature, and waits up to 10 seconds, the same limit as real deliveries. It tells you whether the URL answers, not whether your handler is correct:
|
|
37
|
+
|
|
38
|
+
| Your endpoint answered | Result |
|
|
39
|
+
|------------------------|--------|
|
|
40
|
+
| `2xx` | Reachable. |
|
|
41
|
+
| `4xx` | Reachable. The probe is unsigned, so an endpoint that checks signatures is expected to reject it with `401` or `400`. A `404`, `405` or `410` is flagged, since it usually means a wrong path or a route that does not accept `POST`. |
|
|
42
|
+
| `3xx` | Flagged. Kelviq never follows redirects, so use the final URL. |
|
|
43
|
+
| `5xx`, no answer within 10 seconds, connection refused or DNS failure | Not reachable. Check your server, then verify again. |
|
|
44
|
+
|
|
45
|
+
### Send a test event
|
|
46
|
+
|
|
47
|
+
**Send test event** delivers a sample of the event type you pick through the normal signed delivery path, including retries, so it exercises your signature check and your handler end to end. Test deliveries are marked in the logs, and their envelope carries `"test": true` so your handler can skip side effects:
|
|
48
|
+
|
|
49
|
+
```json
|
|
50
|
+
{
|
|
51
|
+
"id": "…",
|
|
52
|
+
"type": "invoice.paid",
|
|
53
|
+
"created_at": "2026-10-26T06:00:00Z",
|
|
54
|
+
"test": true,
|
|
55
|
+
"data": { "object": { … } }
|
|
56
|
+
}
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
Live events never carry the `test` field. Test deliveries appear in the logs only: they are left out of the delivery statistics and do not affect an endpoint's status or last delivery.
|
|
29
60
|
|
|
30
61
|
---
|
|
31
62
|
|
|
32
63
|
## Inspect and resend deliveries
|
|
33
64
|
|
|
34
|
-
Open **Settings → Webhooks** and select an endpoint to view its delivery logs. Each delivery shows the event type, status, response code, and response body.
|
|
65
|
+
Open **Settings → Webhooks** and select an endpoint to view its delivery logs, or use the **Logs** tab for every endpoint at once. Each delivery attempt shows the event type, status, response code, response time, and response body. A failed attempt that will be retried shows when the next attempt is due; a `4xx` is final and shows as not retried. Logs are kept for 30 days.
|
|
66
|
+
|
|
67
|
+
The **Endpoints** tab summarises deliveries, success rate, failures and average response time for the selected period against the period before it, and flags any endpoint whose latest deliveries are failing. Every attempt is also available from [`GET /webhook/logs/`](/api-reference/webhooks/list-webhook-logs).
|
|
35
68
|
|
|
36
69
|
To retry a delivery:
|
|
37
70
|
|
|
@@ -40,7 +73,7 @@ To retry a delivery:
|
|
|
40
73
|
3. Click **Resend**.
|
|
41
74
|
4. Review the new delivery attempt and its response.
|
|
42
75
|
|
|
43
|
-
Kelviq
|
|
76
|
+
Kelviq automatically retries timeouts, connection failures, and `5xx` or `429` responses, but not other `4xx` or `3xx` responses. Use a manual resend to redeliver those after you fix the endpoint, or to retry immediately instead of waiting for the next automatic attempt.
|
|
44
77
|
|
|
45
78
|
Automatic retries and manual resends can deliver the same event more than once. Process webhooks idempotently using the event `id` or the `webhook-id` header.
|
|
46
79
|
|
|
@@ -60,6 +93,8 @@ Kelviq also retries failed deliveries automatically. A manual resend is useful w
|
|
|
60
93
|
| `subscription.updated` | A subscription's details were modified — including when a cancellation is scheduled for the end of the current period (status stays active; `end_date` is set). |
|
|
61
94
|
| `subscription.cancelled` | A subscription actually reached cancelled status. For a period-end cancellation, this fires later, when the period ends — not at the moment it was scheduled. |
|
|
62
95
|
| `subscription.plan_changed` | A subscription was moved to a different plan. |
|
|
96
|
+
| `subscription.paused` | A customer paused their subscription from the customer portal. The payload includes `paused_at` and `pause_resumes_at`. No other subscription events are sent while it stays paused. |
|
|
97
|
+
| `subscription.resumed` | A paused subscription started billing again, either at its scheduled date or by a resume call. Clear any cached entitlement checks for the customer on both events. |
|
|
63
98
|
| `subscription.trial_will_end` | A subscription's trial period is ending soon. |
|
|
64
99
|
| `feature.usage_alert` | A customer's feature usage crossed a configured threshold. |
|
|
65
100
|
| `invoice.created` | A new invoice was generated. |
|
|
@@ -81,6 +116,10 @@ Kelviq also retries failed deliveries automatically. A manual resend is useful w
|
|
|
81
116
|
|
|
82
117
|
Use your customer identifier or checkout `metadata` to correlate the two events. See [Add metadata to checkout](/checkout/checkout-metadata) for request and webhook examples. Do not treat the checkout redirect as proof that a subscription has been created.
|
|
83
118
|
|
|
119
|
+
### Custom field responses
|
|
120
|
+
|
|
121
|
+
When a checkout session collects [custom fields](/checkout/custom-fields), the customer's responses are included as `custom_fields_data` in `data.object` of `checkout.completed` and of the `order.created`, `order.updated`, and `order.refunded` events for the resulting order. The object is keyed by custom field identifier and is empty (`{}`) when the session collected no custom fields.
|
|
122
|
+
|
|
84
123
|
### Successful invoice payments
|
|
85
124
|
|
|
86
125
|
Kelviq sends `invoice.paid` whenever an invoice is paid, including invoices that are created directly with a `PAID` status. Use this event for payment-driven work such as recording revenue, starting an asynchronous provisioning job, or notifying an internal system.
|
|
@@ -111,7 +150,7 @@ Kelviq does not currently send a separate `payment.failed` event. For a failed c
|
|
|
111
150
|
|
|
112
151
|
Do not remove access when you receive the first `subscription.updated` with `past_due` unless that is your own policy. Use the final subscription status or a live entitlement check to decide when access should end.
|
|
113
152
|
|
|
114
|
-
|
|
153
|
+
Card and UPI AutoPay renewals are retried for up to 14 days. If the payment still fails, the subscription is canceled.
|
|
115
154
|
|
|
116
155
|
### Billing period field names
|
|
117
156
|
|
|
@@ -125,6 +164,14 @@ If you update a subscription with `paymentBehavior: "activate_on_payment"`, the
|
|
|
125
164
|
|
|
126
165
|
Do not provision the new plan from the update API response alone. Read the latest subscription status or query the customer's current entitlements before changing access.
|
|
127
166
|
|
|
167
|
+
### Pauses and resumes
|
|
168
|
+
|
|
169
|
+
A pause sends `subscription.paused` with `status: "paused"`, `paused_at`, and `pause_resumes_at`, which is `null` for an open-ended pause. Treat it like a cancellation for access: entitlement checks already return `false` for a paused customer, so clear any cached result when the event arrives (`client.entitlements.invalidateCache` in Node, `client.entitlements.invalidate_cache` in Python).
|
|
170
|
+
|
|
171
|
+
The subscription is quiet until it resumes. Renewals that fall inside the pause are skipped without `subscription.updated` or invoice events. `subscription.resumed` arrives when billing starts again, at the scheduled date or after a resume call, with `status: "active"` and a new billing period. Usage counters are reset at that point.
|
|
172
|
+
|
|
173
|
+
Both events fire whichever surface made the change: the dashboard, the customer portal, or your API call.
|
|
174
|
+
|
|
128
175
|
### Partial and full refunds
|
|
129
176
|
|
|
130
177
|
`order.refunded` identifies whether the order is partially or fully refunded through its `status`:
|
|
@@ -172,6 +219,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
172
219
|
| `created_at` | `string` (ISO 8601) | UTC timestamp of when the event was created. |
|
|
173
220
|
| `data.object` | `object` | The primary resource affected by the event. |
|
|
174
221
|
| `data.previous_attributes` | `object` | *(Update events only)* The resource's changed attributes before the event. Omitted if not applicable. |
|
|
222
|
+
| `test` | `boolean` | *(Test events only)* `true` when the delivery was triggered with **Send test event**. Absent on live events. |
|
|
175
223
|
|
|
176
224
|
```json
|
|
177
225
|
{
|
|
@@ -212,7 +260,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
212
260
|
},
|
|
213
261
|
"product": {
|
|
214
262
|
"id": "df398021-477b-4e67-972d-c763a2f2ba7b",
|
|
215
|
-
"name": "
|
|
263
|
+
"name": "Acme Analytics"
|
|
216
264
|
},
|
|
217
265
|
"billing_address": {
|
|
218
266
|
"line1": null,
|
|
@@ -226,6 +274,10 @@ The request body is a JSON object with the following top-level fields:
|
|
|
226
274
|
"order_ref": "ABC-123",
|
|
227
275
|
"source": "pricing_page"
|
|
228
276
|
},
|
|
277
|
+
"custom_fields_data": {
|
|
278
|
+
"company-name": "Acme Inc",
|
|
279
|
+
"purchase-order-number": "PO-4821"
|
|
280
|
+
},
|
|
229
281
|
"data": {
|
|
230
282
|
"name": "Geo",
|
|
231
283
|
"email": "geojacob@example.com",
|
|
@@ -295,7 +347,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
295
347
|
|
|
296
348
|
```json
|
|
297
349
|
{
|
|
298
|
-
"id": "
|
|
350
|
+
"id": "3f6a9c2e-1b4d-4e8f-9a7c-5d2e8b1f4a60",
|
|
299
351
|
"type": "order.created",
|
|
300
352
|
"created_at": "2026-04-01T17:36:41Z",
|
|
301
353
|
"data": {
|
|
@@ -314,6 +366,10 @@ The request body is a JSON object with the following top-level fields:
|
|
|
314
366
|
},
|
|
315
367
|
"organization": "9b759915-5387-4e61-90e9-2162318e8d17",
|
|
316
368
|
"is_renewal": false,
|
|
369
|
+
"custom_fields_data": {
|
|
370
|
+
"company-name": "Acme Inc",
|
|
371
|
+
"purchase-order-number": "PO-4821"
|
|
372
|
+
},
|
|
317
373
|
"paid_at": "2026-04-01T17:36:41Z",
|
|
318
374
|
"amount_total": "10.00",
|
|
319
375
|
"amount_total_units": 1000,
|
|
@@ -321,7 +377,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
321
377
|
"subscription_id": "2c78e8f0-892e-406c-9896-18c69d3026c4",
|
|
322
378
|
"product": {
|
|
323
379
|
"id": "df398021-477b-4e67-972d-c763a2f2ba7b",
|
|
324
|
-
"name": "
|
|
380
|
+
"name": "Acme Analytics"
|
|
325
381
|
},
|
|
326
382
|
"plan": {
|
|
327
383
|
"name": "Exc Tax Plan",
|
|
@@ -338,7 +394,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
338
394
|
|
|
339
395
|
```json
|
|
340
396
|
{
|
|
341
|
-
"id": "
|
|
397
|
+
"id": "7c1e4b9a-2d5f-4a3c-8e6b-0f9d2a7c3e51",
|
|
342
398
|
"type": "order.updated",
|
|
343
399
|
"created_at": "2026-04-01T17:36:41Z",
|
|
344
400
|
"data": {
|
|
@@ -364,6 +420,10 @@ The request body is a JSON object with the following top-level fields:
|
|
|
364
420
|
},
|
|
365
421
|
"organization": "9b759915-5387-4e61-90e9-2162318e8d17",
|
|
366
422
|
"is_renewal": false,
|
|
423
|
+
"custom_fields_data": {
|
|
424
|
+
"company-name": "Acme Inc",
|
|
425
|
+
"purchase-order-number": "PO-4821"
|
|
426
|
+
},
|
|
367
427
|
"paid_at": "2026-04-01T17:36:41Z",
|
|
368
428
|
"amount_total": "10.00",
|
|
369
429
|
"amount_total_units": 1000,
|
|
@@ -371,7 +431,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
371
431
|
"subscription_id": "2c78e8f0-892e-406c-9896-18c69d3026c4",
|
|
372
432
|
"product": {
|
|
373
433
|
"id": "df398021-477b-4e67-972d-c763a2f2ba7b",
|
|
374
|
-
"name": "
|
|
434
|
+
"name": "Acme Analytics"
|
|
375
435
|
},
|
|
376
436
|
"plan": {
|
|
377
437
|
"name": "Exc Tax Plan",
|
|
@@ -417,6 +477,10 @@ The request body is a JSON object with the following top-level fields:
|
|
|
417
477
|
},
|
|
418
478
|
"organization": "9b759915-5387-4e61-90e9-2162318e8d17",
|
|
419
479
|
"is_renewal": false,
|
|
480
|
+
"custom_fields_data": {
|
|
481
|
+
"company-name": "Acme Inc",
|
|
482
|
+
"purchase-order-number": "PO-4821"
|
|
483
|
+
},
|
|
420
484
|
"paid_at": "2026-04-01T17:36:41Z",
|
|
421
485
|
"amount_total": "10.00",
|
|
422
486
|
"amount_total_units": 1000,
|
|
@@ -424,7 +488,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
424
488
|
"subscription_id": "2c78e8f0-892e-406c-9896-18c69d3026c4",
|
|
425
489
|
"product": {
|
|
426
490
|
"id": "df398021-477b-4e67-972d-c763a2f2ba7b",
|
|
427
|
-
"name": "
|
|
491
|
+
"name": "Acme Analytics"
|
|
428
492
|
},
|
|
429
493
|
"plan": {
|
|
430
494
|
"name": "Exc Tax Plan",
|
|
@@ -453,16 +517,16 @@ The request body is a JSON object with the following top-level fields:
|
|
|
453
517
|
"object": "subscription",
|
|
454
518
|
"status": "active",
|
|
455
519
|
"plan": {
|
|
456
|
-
"name": "
|
|
520
|
+
"name": "Pro",
|
|
457
521
|
"version": 1,
|
|
458
|
-
"identifier": "
|
|
522
|
+
"identifier": "pro"
|
|
459
523
|
},
|
|
460
524
|
"product": {
|
|
461
525
|
"id": "b4ea7e75-5dbe-4b3b-96e0-9a31dfe5a600",
|
|
462
|
-
"name": "
|
|
526
|
+
"name": "Acme Analytics"
|
|
463
527
|
},
|
|
464
528
|
"amount": "21.24",
|
|
465
|
-
"amount_units":
|
|
529
|
+
"amount_units": 2124,
|
|
466
530
|
"currency": "USD",
|
|
467
531
|
"recurrence": "1 month",
|
|
468
532
|
"start_date": "2026-03-11",
|
|
@@ -519,7 +583,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
519
583
|
},
|
|
520
584
|
"product": {
|
|
521
585
|
"id": "df398021-477b-4e67-972d-c763a2f2ba7b",
|
|
522
|
-
"name": "
|
|
586
|
+
"name": "Acme Analytics"
|
|
523
587
|
},
|
|
524
588
|
"customer": {
|
|
525
589
|
"id": "936cf361-3a4b-454c-a464-41ccc7600c2d",
|
|
@@ -575,7 +639,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
575
639
|
},
|
|
576
640
|
"product": {
|
|
577
641
|
"id": "df398021-477b-4e67-972d-c763a2f2ba7b",
|
|
578
|
-
"name": "
|
|
642
|
+
"name": "Acme Analytics"
|
|
579
643
|
},
|
|
580
644
|
"customer": {
|
|
581
645
|
"id": "936cf361-3a4b-454c-a464-41ccc7600c2d",
|
|
@@ -607,7 +671,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
607
671
|
|
|
608
672
|
```json
|
|
609
673
|
{
|
|
610
|
-
"id": "b9c2e1f0-7d3a-4b8e-a456-
|
|
674
|
+
"id": "b9c2e1f0-7d3a-4b8e-a456-1f2a3b4c5d6e",
|
|
611
675
|
"type": "subscription.plan_changed",
|
|
612
676
|
"created_at": "2026-03-04T11:53:12Z",
|
|
613
677
|
"data": {
|
|
@@ -685,6 +749,94 @@ The request body is a JSON object with the following top-level fields:
|
|
|
685
749
|
}
|
|
686
750
|
```
|
|
687
751
|
|
|
752
|
+
```json
|
|
753
|
+
{
|
|
754
|
+
"id": "c4d1a2b3-9e8f-4a7b-b123-4c5d6e7f8a9b",
|
|
755
|
+
"type": "subscription.paused",
|
|
756
|
+
"created_at": "2026-09-30T10:00:00Z",
|
|
757
|
+
"data": {
|
|
758
|
+
"object": {
|
|
759
|
+
"id": "d1284180-beba-465a-b756-9a300324245e",
|
|
760
|
+
"object": "subscription",
|
|
761
|
+
"status": "paused",
|
|
762
|
+
"paused_at": "2026-09-30T10:00:00Z",
|
|
763
|
+
"pause_resumes_at": "2026-12-31T23:00:00Z",
|
|
764
|
+
"plan": {
|
|
765
|
+
"name": "Pro",
|
|
766
|
+
"version": 4,
|
|
767
|
+
"identifier": "pro"
|
|
768
|
+
},
|
|
769
|
+
"product": {
|
|
770
|
+
"id": "988dba89-0a96-4cb5-870a-34810011c1f1",
|
|
771
|
+
"name": "demo"
|
|
772
|
+
},
|
|
773
|
+
"amount": "29.00",
|
|
774
|
+
"amount_units": 2900,
|
|
775
|
+
"currency": "USD",
|
|
776
|
+
"recurrence": "1 month",
|
|
777
|
+
"start_date": "2026-02-26",
|
|
778
|
+
"end_date": null,
|
|
779
|
+
"billing_period_start_time": "2026-09-26T05:25:11Z",
|
|
780
|
+
"billing_period_end_time": "2026-10-26T05:25:11Z",
|
|
781
|
+
"customer": {
|
|
782
|
+
"id": "798e663f-2fe9-43d7-879f-2549263e20d1",
|
|
783
|
+
"name": "Geo",
|
|
784
|
+
"email": "geo@example.com",
|
|
785
|
+
"customer_id": "geo123",
|
|
786
|
+
"billing_address": {}
|
|
787
|
+
},
|
|
788
|
+
"organization": "5d0bec80-a7c1-41ae-bd24-ea9228500586",
|
|
789
|
+
"created_on": "2026-02-26T05:25:11Z",
|
|
790
|
+
"modified_on": "2026-09-30T10:00:00Z"
|
|
791
|
+
}
|
|
792
|
+
}
|
|
793
|
+
}
|
|
794
|
+
```
|
|
795
|
+
|
|
796
|
+
```json
|
|
797
|
+
{
|
|
798
|
+
"id": "e5f6a7b8-1c2d-4e3f-a456-7b8c9d0e1f2a",
|
|
799
|
+
"type": "subscription.resumed",
|
|
800
|
+
"created_at": "2026-12-31T23:00:00Z",
|
|
801
|
+
"data": {
|
|
802
|
+
"object": {
|
|
803
|
+
"id": "d1284180-beba-465a-b756-9a300324245e",
|
|
804
|
+
"object": "subscription",
|
|
805
|
+
"status": "active",
|
|
806
|
+
"paused_at": null,
|
|
807
|
+
"pause_resumes_at": null,
|
|
808
|
+
"plan": {
|
|
809
|
+
"name": "Pro",
|
|
810
|
+
"version": 4,
|
|
811
|
+
"identifier": "pro"
|
|
812
|
+
},
|
|
813
|
+
"product": {
|
|
814
|
+
"id": "988dba89-0a96-4cb5-870a-34810011c1f1",
|
|
815
|
+
"name": "demo"
|
|
816
|
+
},
|
|
817
|
+
"amount": "29.00",
|
|
818
|
+
"amount_units": 2900,
|
|
819
|
+
"currency": "USD",
|
|
820
|
+
"recurrence": "1 month",
|
|
821
|
+
"start_date": "2026-02-26",
|
|
822
|
+
"end_date": null,
|
|
823
|
+
"billing_period_start_time": "2026-12-31T23:00:00Z",
|
|
824
|
+
"billing_period_end_time": "2027-01-31T23:00:00Z",
|
|
825
|
+
"customer": {
|
|
826
|
+
"id": "798e663f-2fe9-43d7-879f-2549263e20d1",
|
|
827
|
+
"name": "Geo",
|
|
828
|
+
"email": "geo@example.com",
|
|
829
|
+
"customer_id": "geo123",
|
|
830
|
+
"billing_address": {}
|
|
831
|
+
},
|
|
832
|
+
"organization": "5d0bec80-a7c1-41ae-bd24-ea9228500586",
|
|
833
|
+
"created_on": "2026-02-26T05:25:11Z",
|
|
834
|
+
"modified_on": "2026-12-31T23:00:00Z"
|
|
835
|
+
}
|
|
836
|
+
}
|
|
837
|
+
}
|
|
838
|
+
```
|
|
839
|
+
|
|
688
840
|
```json
|
|
689
841
|
{
|
|
690
842
|
"id": "7c6d5e4f-3b2a-4190-8e7d-6c5b4a3f2e1d",
|
|
@@ -696,16 +848,16 @@ The request body is a JSON object with the following top-level fields:
|
|
|
696
848
|
"object": "subscription",
|
|
697
849
|
"status": "trialing",
|
|
698
850
|
"plan": {
|
|
699
|
-
"name": "
|
|
851
|
+
"name": "Pro",
|
|
700
852
|
"version": 1,
|
|
701
|
-
"identifier": "
|
|
853
|
+
"identifier": "pro"
|
|
702
854
|
},
|
|
703
855
|
"product": {
|
|
704
856
|
"id": "b4ea7e75-5dbe-4b3b-96e0-9a31dfe5a600",
|
|
705
|
-
"name": "
|
|
857
|
+
"name": "Acme Analytics"
|
|
706
858
|
},
|
|
707
859
|
"amount": "21.24",
|
|
708
|
-
"amount_units":
|
|
860
|
+
"amount_units": 2124,
|
|
709
861
|
"currency": "USD",
|
|
710
862
|
"recurrence": "1 month",
|
|
711
863
|
"start_date": "2026-08-01",
|
|
@@ -737,7 +889,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
737
889
|
}
|
|
738
890
|
```
|
|
739
891
|
|
|
740
|
-
`data.object` uses the same subscription payload shape as `subscription.created`/`subscription.updated`; the trial's remaining time is in `trial_end`. Kelviq sends this once, a few days before `trial_end
|
|
892
|
+
`data.object` uses the same subscription payload shape as `subscription.created`/`subscription.updated`; the trial's remaining time is in `trial_end`. Kelviq sends this once, a few days before `trial_end`. It's skipped if the subscription has already converted to `active` or has no trial days left.
|
|
741
893
|
|
|
742
894
|
```json
|
|
743
895
|
{
|
|
@@ -822,7 +974,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
822
974
|
"organization": "9b759915-5387-4e61-90e9-2162318e8d17",
|
|
823
975
|
"product": {
|
|
824
976
|
"id": "df398021-477b-4e67-972d-c763a2f2ba7b",
|
|
825
|
-
"name": "
|
|
977
|
+
"name": "Acme Analytics"
|
|
826
978
|
},
|
|
827
979
|
"created_on": "2026-04-02T05:56:33Z",
|
|
828
980
|
"modified_on": "2026-04-02T05:56:33Z"
|
|
@@ -870,7 +1022,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
870
1022
|
"organization": "9b759915-5387-4e61-90e9-2162318e8d17",
|
|
871
1023
|
"product": {
|
|
872
1024
|
"id": "df398021-477b-4e67-972d-c763a2f2ba7b",
|
|
873
|
-
"name": "
|
|
1025
|
+
"name": "Acme Analytics"
|
|
874
1026
|
},
|
|
875
1027
|
"created_on": "2026-04-02T05:56:33Z",
|
|
876
1028
|
"modified_on": "2026-04-02T06:00:00Z"
|
|
@@ -911,7 +1063,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
911
1063
|
},
|
|
912
1064
|
"product": {
|
|
913
1065
|
"id": "df398021-477b-4e67-972d-c763a2f2ba7b",
|
|
914
|
-
"name": "
|
|
1066
|
+
"name": "Acme Analytics"
|
|
915
1067
|
},
|
|
916
1068
|
"subscription_id": "a2951973-aca5-408d-bd9c-1d86827ed463",
|
|
917
1069
|
"order_id": null,
|
|
@@ -977,7 +1129,7 @@ The request body is a JSON object with the following top-level fields:
|
|
|
977
1129
|
|
|
978
1130
|
```json
|
|
979
1131
|
{
|
|
980
|
-
"id": "
|
|
1132
|
+
"id": "e2b8d4f1-6a3c-4f9e-b7d2-9c1a5e3f8b04",
|
|
981
1133
|
"type": "refund.updated",
|
|
982
1134
|
"created_at": "2026-04-02T05:41:30Z",
|
|
983
1135
|
"data": {
|
|
@@ -1402,4 +1554,4 @@ func main() {
|
|
|
1402
1554
|
## Need Help?
|
|
1403
1555
|
|
|
1404
1556
|
- Email us at **hi@kelviq.com**
|
|
1405
|
-
- [Book a demo](https://
|
|
1557
|
+
- [Book a demo](https://cal.com/alok-vats-fkpnc9/30min)
|
|
@@ -0,0 +1,88 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: "WooCommerce"
|
|
3
|
+
slug: "integrations/woocommerce"
|
|
4
|
+
section: "integrations"
|
|
5
|
+
description: "Take payments in your WooCommerce store with Kelviq checkout"
|
|
6
|
+
---
|
|
7
|
+
Add Kelviq as a payment method in your [WooCommerce](https://woocommerce.com) store. Shoppers fill their cart as usual, pay on a secure Kelviq checkout, and come back to your store. Kelviq is the Merchant of Record: it takes the payment, charges the right sales tax or VAT for the shopper's country, and sends the invoice.
|
|
8
|
+
|
|
9
|
+
Kelviq for WooCommerce is for digital products, software and subscriptions. Don't use it to sell physical goods.
|
|
10
|
+
|
|
11
|
+
## How it works
|
|
12
|
+
|
|
13
|
+
1. The shopper places an order and chooses the Kelviq payment method.
|
|
14
|
+
2. They're taken to Kelviq checkout to pay the order total, with cards, Apple Pay, Google Pay, PayPal and the other [payment methods](/checkout/payment-methods) you've turned on.
|
|
15
|
+
3. Kelviq tells your store the payment succeeded, and the shopper returns to the order confirmation page. Before marking the order paid, the plugin checks the payment with the Kelviq API.
|
|
16
|
+
|
|
17
|
+
Coupons are applied in WooCommerce, so the shopper pays the discounted total. Kelviq discount codes are turned off for these checkouts.
|
|
18
|
+
|
|
19
|
+
## Before you start
|
|
20
|
+
|
|
21
|
+
You need:
|
|
22
|
+
|
|
23
|
+
- A WordPress site with WooCommerce 8.0 or later, reachable from the internet over **HTTPS**. Kelviq sends payment confirmations to your site, so it can't be a local or password-protected site.
|
|
24
|
+
- A Kelviq **Server API key**, from **Settings → API keys**.
|
|
25
|
+
- A **one-time plan** that WooCommerce orders are sold under:
|
|
26
|
+
1. Open **Products** and add a product, for example `WooCommerce store`.
|
|
27
|
+
2. Add a plan with a one-time price, for example `WooCommerce order`, and publish it. The price doesn't matter: the shopper always pays the order total.
|
|
28
|
+
3. Copy the plan's **identifier**, for example `woocommerce-order`.
|
|
29
|
+
|
|
30
|
+
Set up everything in [sandbox mode](/guides/sandbox) first, with a sandbox API key and plan. You can then pay with [test cards](/guides/test-payments) before taking real payments.
|
|
31
|
+
|
|
32
|
+
## Install the plugin
|
|
33
|
+
|
|
34
|
+
1. In Kelviq, open **Settings → Integrations**, click **Configure WooCommerce**, then **Download plugin**.
|
|
35
|
+
2. In WordPress, open **Plugins → Add New Plugin → Upload Plugin**.
|
|
36
|
+
3. Choose `kelviq-for-woocommerce.zip`, click **Install Now**, then **Activate**.
|
|
37
|
+
|
|
38
|
+
## Connect it to Kelviq
|
|
39
|
+
|
|
40
|
+
1. In WordPress, open **WooCommerce → Settings → Payments**, and click **Kelviq**.
|
|
41
|
+
2. Tick **Enable Kelviq**.
|
|
42
|
+
3. Choose the **Environment**: **Sandbox** for test payments or **Live** for real ones.
|
|
43
|
+
4. Paste your **Server API key** for that environment.
|
|
44
|
+
5. Enter the **Kelviq plan identifier**.
|
|
45
|
+
6. Choose how **Tax** works:
|
|
46
|
+
- **My prices include tax** (default): the shopper pays exactly your price, and Kelviq takes the tax out of it.
|
|
47
|
+
- **Add tax on top of my prices**: Kelviq adds tax for the shopper's country at checkout.
|
|
48
|
+
7. Optionally, change the **Title** and **Description** shoppers see at checkout.
|
|
49
|
+
8. Click **Save changes**.
|
|
50
|
+
|
|
51
|
+
The plugin checks your key and plan, then creates a webhook endpoint in Kelviq for your store, named `WooCommerce: <your site>`. You'll see **Kelviq is connected** at the top of the page.
|
|
52
|
+
|
|
53
|
+
Kelviq calculates tax, so turn off WooCommerce taxes in **WooCommerce → Settings → General** (untick **Enable tax rates and calculations**). Otherwise shoppers are charged tax twice.
|
|
54
|
+
|
|
55
|
+
## Refunds
|
|
56
|
+
|
|
57
|
+
- **From WooCommerce:** open the order, click **Refund**, enter the amount, and click the **Refund … via** button with your Kelviq title. The refund is made in Kelviq.
|
|
58
|
+
- **From Kelviq:** refund the order in **Sales → Orders**. The refund also appears on the WooCommerce order. A full refund sets the order to **Refunded**.
|
|
59
|
+
|
|
60
|
+
## Order details
|
|
61
|
+
|
|
62
|
+
Each paid order shows:
|
|
63
|
+
|
|
64
|
+
- The Kelviq order ID as the **Transaction ID**.
|
|
65
|
+
- Order notes for each step, for example *Shopper sent to Kelviq checkout* and *Paid with Kelviq*.
|
|
66
|
+
|
|
67
|
+
In Kelviq, each checkout has the WooCommerce order ID and number in its [metadata](/checkout/checkout-metadata) (`wc_order_id`, `wc_order_number`), so you can match orders in both places.
|
|
68
|
+
|
|
69
|
+
## Troubleshooting
|
|
70
|
+
|
|
71
|
+
Errors are shown at the top of the Kelviq settings page, and on the order as order notes. For more detail, tick **Debug log** and open **WooCommerce → Status → Logs** (source `kelviq`).
|
|
72
|
+
|
|
73
|
+
| Problem | What to do |
|
|
74
|
+
| --- | --- |
|
|
75
|
+
| Kelviq did not accept the API key | Paste a Server API key from **Settings → API keys** for the environment you chose. A sandbox key doesn't work in Live, and the other way around. |
|
|
76
|
+
| No plan "…" in this environment | Check the plan identifier in **Products**, and that the plan is published in the same environment as your key. |
|
|
77
|
+
| Could not set up payment confirmations | Your site isn't reachable from the internet over HTTPS, for example it's a local site or behind a password. Put the site online, then click **Save changes** again. |
|
|
78
|
+
| Kelviq doesn't show at checkout | Tick **Enable Kelviq**, and fill in the API key and plan identifier. |
|
|
79
|
+
| We could not start the payment | The order note says why, for example a currency Kelviq doesn't support. |
|
|
80
|
+
| Order stays "Pending payment" after paying | Open **Settings → Webhooks** in Kelviq, find `WooCommerce: <your site>`, and check its deliveries. Resend a failed one. The order is also confirmed when the shopper returns to your store. |
|
|
81
|
+
|
|
82
|
+
## Disconnect
|
|
83
|
+
|
|
84
|
+
Untick **Enable Kelviq** and save to stop offering it at checkout. When you delete the plugin, it also deletes its webhook endpoint in Kelviq.
|
|
85
|
+
|
|
86
|
+
## Prefer code?
|
|
87
|
+
|
|
88
|
+
Use the [checkout API](/api-reference/checkout/create-a-checkout-session) and [webhooks](/guides/webhooks) to build your own integration.
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: "Zapier"
|
|
3
|
+
slug: "integrations/zapier"
|
|
4
|
+
section: "integrations"
|
|
5
|
+
description: "Connect Kelviq to Zapier to automate work across your other apps"
|
|
6
|
+
---
|
|
7
|
+
Use Zapier to connect Kelviq to the rest of your tools without writing code, for example to send a team message or update a spreadsheet when something happens in Kelviq.
|
|
8
|
+
|
|
9
|
+
<img src="/images/settings/zapier-integration.webp" alt="The Integrations settings page with the Zapier card and its Configure in Zapier button" />
|
|
10
|
+
|
|
11
|
+
## Connect Kelviq to Zapier
|
|
12
|
+
|
|
13
|
+
1. Open **Settings → Integrations**.
|
|
14
|
+
2. Click **Configure in Zapier**. Zapier opens in a new tab.
|
|
15
|
+
3. Sign in to Zapier, or create a free account, and accept the invitation to use the Kelviq app.
|
|
16
|
+
4. In Zapier, create a Zap and choose **Kelviq** as the app. Pick the event you want, then connect your Kelviq account when Zapier asks.
|
|
17
|
+
|
|
18
|
+
The Kelviq app on Zapier is available by invitation, so it won't show up in Zapier's app search until you've accepted the invitation from step 3.
|
|
19
|
+
|
|
20
|
+
## Prefer code?
|
|
21
|
+
|
|
22
|
+
If you'd rather handle events in your own backend, use [webhooks](/guides/webhooks). Kelviq sends each event with its full payload to your server.
|
|
@@ -0,0 +1,59 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: "Account and funds terms"
|
|
3
|
+
slug: "legal/account-and-funds"
|
|
4
|
+
section: "legal"
|
|
5
|
+
description: "Where seller funds sit, reserves, suspensions, billing records, and moving to another provider"
|
|
6
|
+
---
|
|
7
|
+
This page summarises how the [Seller Agreement](/legal/master-service-agreement) applies to your account. If anything here conflicts with the agreement, the agreement controls.
|
|
8
|
+
|
|
9
|
+
## Where does the money actually sit?
|
|
10
|
+
|
|
11
|
+
During processing, the money appears in Stripe balances. It first appears in Kelviq's Stripe platform balance. After the separate transfer, your share appears in your Stripe connected-account balance. Stripe then sends the payout to your registered bank account.
|
|
12
|
+
|
|
13
|
+
A Kelviq payout balance is not a bank deposit, escrow account, or insured investment. It represents amounts due under the Seller Agreement and can change because of refunds, chargebacks, fees, currency conversion, or a valid reserve.
|
|
14
|
+
|
|
15
|
+
You can track this flow in two places:
|
|
16
|
+
|
|
17
|
+
- The Kelviq **Payouts** dashboard shows processing funds, cleared funds, withdrawals, and payout history.
|
|
18
|
+
- Your Stripe connected-account details show the verified business and bank account used for payouts.
|
|
19
|
+
|
|
20
|
+
Read [Payouts](/payouts/overview) for the dashboard workflow.
|
|
21
|
+
|
|
22
|
+
## What protects my funds if Kelviq closes my account?
|
|
23
|
+
|
|
24
|
+
The Seller Agreement sets out Kelviq's payout obligations and when a payout can be delayed or reserved:
|
|
25
|
+
|
|
26
|
+
- Completed transactions move to your available balance after processing.
|
|
27
|
+
- Final payouts remain due if Kelviq ends the service, subject to open disputes and a permitted reserve.
|
|
28
|
+
- A reserve must have a stated amount or percentage and an expected duration.
|
|
29
|
+
- A post-termination reserve can remain in place for up to 180 days to cover refunds, chargebacks, or other transaction liabilities.
|
|
30
|
+
|
|
31
|
+
This is not a guarantee that nothing can go wrong. A processor failure, bank delay, dispute, compliance action, or insolvency can still affect the timing or recovery of funds. What you do have is a written payment flow, transaction records, and contractual payout terms against which you can check Kelviq's handling of your money. Review [Payout Terms](/legal/master-service-agreement#7-payout-terms) and [Reserves and Holdbacks](/legal/master-service-agreement#8-reserves-and-holdbacks) for the controlling language.
|
|
32
|
+
|
|
33
|
+
## How much notice will I get before a suspension?
|
|
34
|
+
|
|
35
|
+
There is no single advance-notice period for every suspension, including every non-fraud suspension. Kelviq may need to act quickly because of suspected fraud, prohibited activity, failed verification, a legal requirement, a payment-network instruction, or a restriction on the connected Stripe account.
|
|
36
|
+
|
|
37
|
+
The 30-day notice in the Seller Agreement applies when Kelviq terminates an account for convenience. It does not apply to the grounds for immediate termination listed in that agreement. If you believe a policy suspension or termination was made in error, you can appeal it. Kelviq responds to appeals within 10 business days under the [Acceptable Use Policy](/legal/approved-prohibited-policy#83-appeal-process).
|
|
38
|
+
|
|
39
|
+
### Will my customers' subscriptions cancel immediately?
|
|
40
|
+
|
|
41
|
+
Not in every case. A suspension and a subscription cancellation are separate actions. However, Kelviq may need to block checkout or future renewals, depending on why the account was restricted. The Seller Agreement does not promise uninterrupted subscription collection during a suspension. If a notice does not clearly say which functions are affected, contact [support@kelviq.com](mailto:support@kelviq.com) before making changes for your customers.
|
|
42
|
+
|
|
43
|
+
## Where do the Stripe Customer and Subscription records live?
|
|
44
|
+
|
|
45
|
+
Kelviq manages the buyer-facing Stripe Customer, PaymentIntent, invoice, and Subscription records on its Stripe platform account. Your Stripe Express connected account receives transfers and payouts; it does not receive an independent copy of every platform billing object.
|
|
46
|
+
|
|
47
|
+
An ID such as `cus_...` or `sub_...` points to an object inside the Stripe account where it was created. It cannot simply be reassigned to another Stripe account. Under the [Seller Agreement](/legal/master-service-agreement#111-buyer-data), Kelviq controls buyer payment and transaction data in its role as Merchant of Record. You still own your product and content, and Kelviq provides the buyer information needed for fulfillment and customer support.
|
|
48
|
+
|
|
49
|
+
## Can I move to another provider?
|
|
50
|
+
|
|
51
|
+
A billing migration is possible in some cases, but it is not an automatic account transfer. Contact [support@kelviq.com](mailto:support@kelviq.com) before closing your Kelviq account or disconnecting Stripe. Kelviq will review the request with Stripe and the receiving provider, then explain what can be transferred.
|
|
52
|
+
|
|
53
|
+
Stripe supports secure exports of eligible card data to a PCI DSS Level 1 payment processor. Some credentials, including cards saved through Link, cannot be exported. Subscription records and payment history also need to be mapped or recreated in the new billing system; moving card data alone does not move an active subscription.
|
|
54
|
+
|
|
55
|
+
Migration scope and timing depend on the receiving provider, Stripe's requirements, applicable privacy rules, and any unresolved refunds, disputes, or reserves. See [Stripe's payment-data export process](https://docs.stripe.com/get-started/data-migrations/pan-export) for the processor-level requirements.
|
|
56
|
+
|
|
57
|
+
## Questions about your account
|
|
58
|
+
|
|
59
|
+
For an account-specific explanation of a payout, reserve, suspension, or migration, email [support@kelviq.com](mailto:support@kelviq.com). Include your Kelviq business name and the relevant transaction, payout, or subscription IDs, but never send a full card number or CVC.
|