Terms of use

What Spend7 is

Spend7 scores a payment intent that has not yet been executed. Given an amount, a merchant, an agent identifier and a rail, it evaluates the spend caps and merchant lists configured on the account, compares the payment against that account’s own recorded history, applies protocol checks where the rail supplies fields to check, and returns a score, a decision of allow, flag or deny, and the signals that produced it. It records each decision with the version and hash of the ruleset that produced it.

What it is not

Spend7 is not a payment processor, a payment facilitator, a bank, or a party to any payment. It never holds a payment credential, never initiates a transfer, and never settles. A decision is advice to the system that called for it; whether the payment happens is entirely that system’s doing. An allow is not a guarantee that a payment is legitimate, and a deny does not stop a payment; only your client can do that.

Spend7 is not insurance and does not underwrite losses. Chargeback-assist ships today: raise a claim against any scored payment and get the evidence packet. An underwritten liability backstop (Spend7 absorbing a share of a loss on a payment it scored as low risk) is not offered and is not priced. It needs an insurance and legal decision before anyone should rely on it.

Scope of the scoring

Behavioural signals are computed from what the account has recorded through Spend7, and from nothing else. An account with little history produces a score with correspondingly little to go on, and the response says so. Below the baseline threshold the check reports that no baseline exists rather than treating the absence of evidence as evidence of normality.

Protocol checks operate only on the fields you send. If an x402 quote’s maxAmountRequiredis not supplied, an overrun cannot be detected; if an AP2 mandate’s ceiling is not supplied, a cart overrun cannot be detected. A clean result on an intent that omitted the rail block means the rail was not checked, not that the rail was sound.

Cross-account graph signals are computed from payments other Spend7 accounts have recorded. They are observations about activity on this platform, not statements about a merchant’s conduct generally, and a merchant with little platform activity produces no graph signal either way.

Evidence packets

A chargeback-assist packet reproduces what was recorded at the time of a scored payment, including the ruleset hash then in force. It attests to what Spend7 decided and on what basis. It does not attest that the underlying facts you sent were accurate, it is not a finding of fraud, and it binds no payment network, issuer or merchant. Whether a dispute succeeds is a matter for the parties to it.

Acceptable use

Send identifiers you are entitled to send. Do not use the service to build a picture of a counterparty you have no relationship with, and do not send payment credentials, card numbers or private keys. Spend7 has no use for them and no field that expects them.

Availability and billing

The free tier is offered without warranty of availability. Paid plans are billed monthly in advance, with metered usage above the included allowance charged in arrears. Usage above the allowance is metered rather than blocked, because a hard stop in front of your agents’ payments is worse for you than an overage line. Subscriptions can be cancelled at any time and run to the end of the paid period.

Liability

Spend7 is provided as is. To the extent permitted by law, liability arising from use of the service is limited to the fees paid in the twelve months preceding the claim. Losses arising from payments your systems executed, or declined to execute, are not recoverable from Spend7.