Core capabilityOnline payment checkoutAccept a customer payment through a hosted or integrated checkout. 4.8 points maximum | Supported4.8 / 4.8 pts Hosted Checkout and Payment Links support online collection. Official documentation · Oct 15, 2026Source ↗ |
|---|
Core capabilityCards plus alternative methodsOffer card acceptance and at least one supported wallet or bank-payment method. 4.8 points maximum | Supported4.8 / 4.8 pts Cards and multiple alternative payment methods are documented. Official documentation · Oct 15, 2026Source ↗ |
|---|
Depth checkPartial refundsRefund less than the original payment and retain the remaining balance. 7.2 points maximumAsk for a demonstrationRefund one item from a multi-item payment and show the remaining refundable amount. A scenario to run with the supplier; not a completed product test. | Supported7.2 / 7.2 pts The Refunds API supports repeated partial refunds up to the original total. Official documentation · Oct 15, 2026Source ↗ |
|---|
Depth checkCustomer authentication controlsSupport an additional cardholder authentication flow such as 3D Secure. 7.2 points maximumAsk for a demonstrationRun a payment that requires cardholder authentication and show the resulting status. A scenario to run with the supplier; not a completed product test. | Supported7.2 / 7.2 pts The payment flow supports automatic or explicitly requested 3D Secure authentication. Official documentation · Oct 15, 2026Source ↗ |
|---|
Core capabilityInvoice-based collectionCreate or send an invoice for customer payment. 3.2 points maximum | Supported3.2 / 3.2 pts Stripe Invoicing is separately priced from basic card processing. Official documentation · Oct 15, 2026Source ↗ |
|---|
Core capabilityRecurring customer chargesSchedule repeat payments or subscriptions using stored payment credentials. 3.2 points maximum | Supported3.2 / 3.2 pts Subscription management uses the separately priced Billing product. Official documentation · Oct 15, 2026Source ↗ |
|---|
Depth checkFailed recurring payment recoveryRetry a failed renewal or provide a recovery workflow for an unpaid recurring charge. 4.8 points maximumAsk for a demonstrationFail a renewal and show the retry or payment recovery sequence. A scenario to run with the supplier; not a completed product test. | Supported4.8 / 4.8 pts Subscription billing supports retries and configured handling after retries are exhausted. Official documentation · Oct 15, 2026Source ↗ |
|---|
Depth checkStop or pause recurring billingCancel or suspend future recurring charges without erasing payment history. 4.8 points maximumAsk for a demonstrationStop a subscription and show its history and next-charge state. A scenario to run with the supplier; not a completed product test. | Supported4.8 / 4.8 pts Subscriptions can cancel immediately or at the end of the billing period. Official documentation · Oct 15, 2026Source ↗ |
|---|
Core capabilityTransaction-level reportsInspect payment, refund and fee records for reconciliation. 3.2 points maximum | Supported3.2 / 3.2 pts Payment and balance reporting exposes transaction detail. Official documentation · Oct 15, 2026Source ↗ |
|---|
Core capabilityPayout or settlement reportingConnect transactions with the settlement or payout reported by the provider. 3.2 points maximum | Supported3.2 / 3.2 pts Payout reconciliation reports connect activity with payouts. Official documentation · Oct 15, 2026Source ↗ |
|---|
Depth checkGross, fees and net reconciliationInspect transaction or settlement records distinguishing gross collections, fees and net proceeds. 4.8 points maximumAsk for a demonstrationTrace a payout to gross payments, fees and net proceeds. A scenario to run with the supplier; not a completed product test. | Supported4.8 / 4.8 pts Stripe financial reports expose payment, fee and balance activity. Official documentation · Oct 15, 2026Source ↗ |
|---|
Depth checkDispute evidence workflowReceive a dispute and submit or manage supporting evidence through a supported workflow. 4.8 points maximumAsk for a demonstrationOpen a dispute and show where evidence and response deadlines are managed. A scenario to run with the supplier; not a completed product test. | Supported4.8 / 4.8 pts Disputes accept evidence through the Dashboard or API. Official documentation · Oct 15, 2026Source ↗ |
|---|
Core capabilityPayment APICreate or manage payment transactions using a documented developer API. 2.4 points maximum | Supported2.4 / 2.4 pts Payment APIs and SDKs are documented. Official documentation · Oct 15, 2026Source ↗ |
|---|
Core capabilityPrebuilt checkout or connectorsUse a prebuilt payment component, checkout or supported connector. 2.4 points maximum | Supported2.4 / 2.4 pts Hosted Checkout and prebuilt payment UI are available. Official documentation · Oct 15, 2026Source ↗ |
|---|
Depth checkWebhook delivery recoveryDocument delivery retries or a supported way to recover failed event notifications. 3.2 points maximumAsk for a demonstrationMake an event endpoint fail and show retry or replay behavior. A scenario to run with the supplier; not a completed product test. | Not verified0–3.2 / 3.2 pts The reviewed documentation does not establish this specific workflow: webhook delivery recovery. Not verified · Oct 15, 2026Source ↗ |
|---|
Depth checkDuplicate payment request protectionUse a documented idempotency or duplicate-request mechanism when retrying payment requests. 4 points maximumAsk for a demonstrationSubmit the same payment request twice and show how duplication is prevented. A scenario to run with the supplier; not a completed product test. | Supported4 / 4 pts Idempotency keys preserve the response when a payment API request is retried. Official documentation · Oct 15, 2026Source ↗ |
|---|
Core capabilityMachine-learning fraud screeningUse explicitly documented machine learning to assess payment fraud risk. 2.4 points maximum | Supported2.4 / 2.4 pts Radar explicitly uses machine learning to evaluate payment fraud risk. Official documentation · Oct 15, 2026Source ↗ |
|---|
Core capabilityAI payment acceptance optimizationUse documented AI or machine learning to improve authorization, authentication or retry decisions. 2.4 points maximum | Supported2.4 / 2.4 pts The reviewed AI record documents payment-acceptance optimization; optional product fees can apply. Official documentation · Oct 15, 2026Source ↗ |
|---|
Depth checkExplain machine-learning risk flagsExpose risk indicators, reasons or review context for a machine-learning risk decision. 3.2 points maximumAsk for a demonstrationOpen an ML-flagged transaction and show the information available to a reviewer. A scenario to run with the supplier; not a completed product test. | Supported3.2 / 3.2 pts Radar risk evaluation exposes risk levels and review context for transactions. Official documentation · Oct 15, 2026Source ↗ |
|---|
Depth checkHuman control over AI risk handlingAllow a merchant to review, override or configure the handling of machine-learning risk decisions. 4 points maximumAsk for a demonstrationShow how staff review or change the handling of an ML risk flag. A scenario to run with the supplier; not a completed product test. | Supported4 / 4 pts Radar supports review, allow lists and merchant rules alongside ML risk decisions. Official documentation · Oct 15, 2026Source ↗ |
|---|
Depth checkMeasure AI risk-model false positives on labelled paymentsDemonstrate “Measure AI risk-model false positives on labelled payments” with a sample record; show the result, permissions and required plan. 2.5 points maximumAsk for a demonstrationDemonstrate “Measure AI risk-model false positives on labelled payments” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test. | Not verified0–2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source ↗ |
|---|
Depth checkAuthorise now and capture funds laterDemonstrate “Authorise now and capture funds later” with a sample record; show the result, permissions and required plan. 2.5 points maximumAsk for a demonstrationDemonstrate “Authorise now and capture funds later” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test. | Supported2.5 / 2.5 pts An eligible PaymentIntent in requires_capture can be captured later, up to its capturable amount. PaymentIntents API; supported payment methods; authorisation remains subject to expiry and capture limits. Official documentation · Oct 21, 2026Source ↗ |
|---|
Depth checkAccept a partial card authorisationDemonstrate “Accept a partial card authorisation” with a sample record; show the result, permissions and required plan. 2.5 points maximumAsk for a demonstrationDemonstrate “Accept a partial card authorisation” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test. | Not verified0–2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source ↗ |
|---|
Depth checkIncrease an existing eligible authorisationDemonstrate “Increase an existing eligible authorisation” with a sample record; show the result, permissions and required plan. 2.5 points maximumAsk for a demonstrationDemonstrate “Increase an existing eligible authorisation” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test. | Supported2.5 / 2.5 pts Eligible uncaptured payments support requests to increase their authorised amount. PaymentIntents API; requires_capture and incremental_authorization_supported must be true; issuer approval and attempt limits apply. Official documentation · Oct 21, 2026Source ↗ |
|---|
Depth checkRefresh network tokens after a card replacementDemonstrate “Refresh network tokens after a card replacement” with a sample record; show the result, permissions and required plan. 2.5 points maximumAsk for a demonstrationDemonstrate “Refresh network tokens after a card replacement” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test. | Not verified0–2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source ↗ |
|---|
Depth checkConfigure the customer bank-statement descriptorDemonstrate “Configure the customer bank-statement descriptor” with a sample record; show the result, permissions and required plan. 2.5 points maximumAsk for a demonstrationDemonstrate “Configure the customer bank-statement descriptor” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test. | Supported2.5 / 2.5 pts Card charges can combine an account-level statement prefix with a transaction-specific suffix. Latin-character and length rules apply; dynamic suffixes are card-only; issuing banks control final display. Official documentation · Oct 21, 2026Source ↗ |
|---|
Depth checkRestrict API keys to specified payment operationsDemonstrate “Restrict API keys to specified payment operations” with a sample record; show the result, permissions and required plan. 2.5 points maximumAsk for a demonstrationDemonstrate “Restrict API keys to specified payment operations” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test. | Not verified0–2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source ↗ |
|---|
Depth checkTrace and resolve a failed merchant payoutDemonstrate “Trace and resolve a failed merchant payout” with a sample record; show the result, permissions and required plan. 2.5 points maximumAsk for a demonstrationDemonstrate “Trace and resolve a failed merchant payout” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test. | Not verified0–2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source ↗ |
|---|