1.Commercial Overview & Transparency
PayloadAPI provides a transparent, developer-first API marketplace connecting API consumers with verified API providers. We believe pricing, cancellations, and refunds should be predictable, fair, and free of dark patterns.
This Refund and Service Level Agreement (SLA) Policy governs all paid subscriptions, usage tiers, and credit adjustments on PayloadAPI. This policy operates in conjunction with our Terms of Service and Privacy Notice.
2.7-Day Self-Serve Refund Policy
We understand that evaluating an API requires real-world testing in your software architecture. If an API does not meet your requirements, you are entitled to a full 100% refund on your subscription fee within seven (7) calendar days of initial purchase or plan upgrade.
Self-Serve Guarantee: You do not need to wait for email approval or submit support tickets. Eligible subscriptions feature a direct Request Refund button inside your Workspace console (Workspace > Subscriptions > Subscription Detail > Request Refund) that calculates eligibility and submits a refund request against the original payment.
Eligible refund requests go to the original processor and original payment method. Provider review, approval and completion can take time. We show a pending status until the outcome is confirmed; your financial institution determines when the refund appears.
3.Eligibility Criteria & Quota Thresholds
To prevent fraudulent scraping and resource exploitation while protecting legitimate testing, self-serve refunds require satisfying two transparent conditions:
- Time Window: The refund must be requested within seven (7) calendar days (168 hours) of the subscription order timestamp.
- Quota Consumed: Less than ten percent (10.0%) of the plan's included meter quota (requests, tokens, or compute units) must have been consumed during the current cycle.
The Workspace refund interface displays a live diagnostic breakdown showing exact consumed units, remaining time, and eligibility status before you confirm.
4.Service Level Agreements (SLA) & Reliability Credits
4.1 Platform Edge Availability Target (99.95%)
The PayloadAPI Edge Gateway is distributed across 300+ edge locations worldwide. We commit to a minimum monthly data plane uptime of 99.95%.
4.2 Outage Credit Schedule
If edge gateway availability or a verified upstream provider with a contracted SLA falls below commitments in any given calendar month, affected subscribers are entitled to service credits:
- 99.00% to 99.94% Uptime: 10% credit applied against the monthly subscription fee.
- 95.00% to 98.99% Uptime: 25% credit applied against the monthly subscription fee.
- Below 95.00% Uptime: 50% credit applied against the monthly subscription fee.
Service credits are automatically applied against your subsequent billing cycle or overage invoice.
5.How to File an SLA Outage Claim
SLA claims can be submitted directly within your Workspace:
- Navigate to
Workspace > Subscriptionsand select the affected API subscription. - Click File SLA Claim to open the incident modal.
- Specify the Incident Start and End timestamps, select the affected endpoint, and provide relevant error telemetry (e.g., HTTP 5xx responses or timeout traces).
Our automated telemetry auditing engine correlates your report against edge routing logs and upstream probe health checks within forty-eight (48) hours. Verified claims automatically apply credit to your organization ledger.
6.Subscription Cancellation & Billing Periods
You may cancel your API subscription at any time directly through the Workspace console:
- No Lock-in: There are no cancellation fees, hidden termination penalties, or minimum commitment periods for standard tiers.
- Continued Access: When you cancel a subscription, your API credentials and remaining monthly quota remain fully active through the conclusion of the paid billing period.
- No Auto-Renewal: Upon cycle completion, the subscription transitions to expired status, and no further recurring charges will be billed.
7.Hard Quotas & Overage Protections
7.1 Zero Surprise Billing
To prevent unexpected overage bills, all plans enforce hard request and meter caps by default at the edge data plane. When your quota limit is reached, requests return HTTP 429 (PX_QUOTA_EXCEEDED) without incurring charges.
7.2 Opt-In Overages & Strict Budget Caps
If you choose to enable overages for continuous service availability, you must explicitly set a maximum monthly budget cap in your Workspace. Once this cap is reached, requests are safely throttled until the next cycle or until you adjust your budget.
8.Payment Providers & Receipts
For purchases processed through Paddle, Paddle acts as merchant of record and handles the corresponding tax records, receipts and refund processing. Direct PayPal, when offered, is a separate PayloadAPI payment flow with its own billing and tax records.
Your receipt identifies the original processor. A PayPal option inside Paddle checkout is a Paddle purchase. For an unresolved Paddle billing issue, contact Paddle support at help.paddle.com.
9.Provider Settlements & Rolling Reserves
PayloadAPI charges a flat 10% platform commission on collected net paid usage. Provider disbursements are structured to accommodate consumer refund windows and chargeback disputes:
- Verified Low-Risk Providers: 90% of net earnings mature seven days after earning time; the remaining 10% mature after 28 days.
- Standard Providers: Net earnings mature 28 days after earning time.
- Refund Deductions: Reversals follow the original publisher allocation. Refunds of unused service credit do not reverse unrelated publisher earnings. Retained collection fees on unused credit refunds are paid by the platform.
Publisher net earnings equal 90% of the eligible API service subtotal, excluding tax, minus actual allocated collection fees. Payout eligibility additionally requires known fees and receipt of the corresponding processor funds. Withdrawals have a $50 minimum, admin review, and checks for holds, deficits, reconciliation and cleared cash. The platform pays outgoing disbursement fees. These holding periods do not promise a payment date.
Unused prepaid service credit refunds first reserve spendable funds and reconcile completed usage. Refunds may be split across original purchases and processors. Funds remain reserved while a result is uncertain. SLA service credits are non-cash adjustments and are separate from processor refunds.
10.Non-Refundable Items & Abuse Prevention
Refunds are not granted in the following scenarios:
- Requests submitted more than seven (7) days after the initial transaction date, unless governed by an approved SLA outage claim.
- Subscriptions where more than 10.0% of the included quota was consumed during the billing cycle.
- Accounts suspended or terminated due to violations of our Acceptable Use Policy (e.g., distributing malware, credential stuffing, scraping, or deliberate denial of service).
- Custom enterprise contracts with bespoke billing schedules that explicitly override standard marketplace refund terms.
11.Billing Support & Inquiries
For questions regarding billing reconciliations, charge discrepancies, or manual refund reviews, our dedicated finance team is available to assist:
- Billing Support:
info@payloadapi.com - General Support:
info@payloadapi.com - Workspace Console: Submit tickets directly from
Workspace > Help & Support