llm-bench — Off-session payment mandate

KAPUA Labs LLC 30 N Gould St Ste R, Sheridan, WY 82801, United States

This document is the separate authorisation that Terms of Service §14 requires before we may charge a stored payment method when you are not present. It authorises nothing except automatic recharge, and it takes effect only if you turn automatic recharge on. It creates no charge that §14 and the Pricing Terms do not already describe; where this document and the Terms differ, the Terms govern.

You do not need to give this authorisation to use the Service. Automatic recharge is off by default. Without it you buy credit yourself, when you choose to, and nothing is ever charged without you present.

1. What you are authorising, and how you give it

You authorise KAPUA Labs LLC to charge the payment method stored on your Account, without you being present and without asking you first, to buy Service credit on your behalf, whenever the conditions in §2 are met — until you withdraw this authorisation under §7.

You give this authorisation by turning automatic recharge on. There is no separate step: switching it on, in your Account’s billing settings, is the act of authorising these charges, and we record it against the version of this document shown to you at the time. We will not turn automatic recharge on without it — a request that does not accept this document is refused and changes nothing.

These are recurring charges of variable amount and irregular timing. They are not a subscription and they follow no calendar: how often they occur depends entirely on how fast you use the Service.

Your card details are entered directly into our payment processor’s hosted forms and are stored by the processor. They never reach our systems (Terms of Service §14), and this authorisation does not change that.

2. When we charge, and how much

You set two figures, and you may change either at any time:

When your available credit falls to or below your threshold, we charge your stored payment method for the recharge amount plus the credit-purchase fee set out in Pricing Terms §2, and add the recharge amount to your credit balance. The fee is the same fee as on any other credit purchase; automatic recharge neither adds to it nor discounts it.

So the sum charged to your card is larger than the credit you receive, by exactly that fee. On a $50 recharge you are charged $52.75 and receive $50 of credit.

A recharge is triggered by your usage, not by a clock, and takes effect within a few minutes of the balance falling to your threshold.

3. The limits that bind us

These bound what this authorisation can cost you. They apply whether or not you set a figure of your own.

The two-times rule exists for your protection: a recharge amount at or below your threshold would leave your balance still under the threshold after the charge landed, triggering another one immediately.

Reaching a limit stops the charge. It never results in a larger charge, a partial charge, or a charge that is queued and taken later.

4. What you receive, and what happens to it

Each recharge buys Service credit on the terms in Pricing Terms §2: credit expires twelve months after the purchase that created it, and where you hold credit from more than one purchase the oldest is spent first.

Credit is a prepayment for Service usage. It is not a deposit. Credit you have bought but not used is refundable on request, less the purchase fee, as Pricing Terms §2.3 describes; a refund requires automatic recharge to be off first, so that it is not bought back (Terms of Service §14).

5. If a payment fails

If your card is declined, we do not present it again for that top-up. Nothing further is charged, no credit is added, and your Account continues to work on whatever credit it still holds until that runs out.

We do not treat a declined card as something to keep trying. Repeatedly presenting a declined card is how a card issuer locks the card out, and it would do that to the card of the customer least able to absorb it. Where a payment fails for a reason that is not a decline of your card — the payment processor was unavailable, or returned a temporary error — it may be attempted again a small number of times over the following days; a decline is not retried on that schedule.

We do not notify you that this has happened, and you should not rely on being told. We do not send an email or any other message about a failed top-up. If your Account depends on automatic recharge, check your balance and your billing settings rather than waiting for a message.

⚠ The reason for a particular failure is not always visible to you. Where we can record it we do, and it appears in your billing settings; where the payment was attempted on our behalf by the provider that holds your card, we may hold no record of the reason at all. In that case the observable fact is the one that matters: no credit was added.

6. Authentication

Some cards, in some countries, require the cardholder to authenticate a payment personally. Such a payment cannot be completed while you are away, and we do not attempt it: an automatic recharge that needs your authentication is stopped rather than left open for you to complete later. Automatic recharge is switched off and you buy credit yourself, present, in the ordinary way.

7. Withdrawing this authorisation

You may withdraw this authorisation at any time, for any reason, without notice or charge.

Turning automatic recharge off withdraws it, exactly as turning it on gave it. Clear the threshold and the recharge amount in your Account’s billing settings, or send PUT /api/billing/v1/auto-recharge on the billing API with both figures cleared. Either route withdraws it; neither is a fallback for the other. The withdrawal is recorded alongside the acceptance it withdraws.

Withdrawal takes effect immediately and stops all future automatic charges. It does not reverse a charge already made, does not refund credit already bought, and does not cancel your Account — you can still buy credit yourself whenever you choose. Removing the stored payment method has the same practical effect, because there is then nothing to charge.

If you later turn automatic recharge on again, you give this authorisation again, under whatever version of this document is current then.

We may also stop acting on this authorisation ourselves at any time — for example under §5, or if we cease to offer automatic recharge.

8. Who may give this authorisation

This authorisation may be given by any person authorised to bind the Account holder, and it may be given through either of the ways the Service accepts instructions: signed in to the Account, or by an Account credential issued by you and acting on your behalf. A credential you issue may already purchase credit and charge your stored payment method on request; this mandate is given the same way.

We record which. Every acceptance is stored with the version of this document accepted, the time, and either the person who accepted it or the identity of the credential that did (Terms of Service §1’s authority-to-bind representation applies in both cases). We do not record a person where none was present, rather than attributing the act to someone who was not there.

If you would rather this mandate could only be given by a named person, do not issue credentials with billing permissions.

9. What this authorisation does not cover

For the avoidance of doubt, this document authorises only the automatic credit purchases described above. It does not authorise:

• charging you for usage — usage draws down credit you already hold, and is never a card charge;
• any subscription or tier fee, which is billed separately and on its own terms;
• any charge after you withdraw this authorisation under §7;
• any charge exceeding the limits in §3;
• storing your card details on our systems (§1).

10. Record of your acceptance

We keep a record of this acceptance for as long as we may need to evidence it, together with the version of this document you accepted. That record outlives the person and the credential that gave it, and is retained after the Account closes; the incidental details captured alongside it — such as the network address the acceptance came from — are erased on request in line with Privacy Policy §8.

If we change this document we will publish a new version. A new version does not carry your acceptance forward: automatic recharge is gated on a current acceptance, so a superseded mandate stops authorising charges rather than silently continuing to.

Version 2026-09-14. Prepared by KAPUA Labs LLC. This document is the separate off-session authorisation required by Terms of Service §14; the Terms are the operative instrument. This version replaces the fixed monthly purchase ceiling in §3 with the per-Account ceiling shown on the Billing page, and aligns §4 with the refund of unused credit in Pricing Terms §2.3.