For the complete documentation index, see llms.txt. This page is also available as Markdown.

Subscription Detection

MRS Subscription Detection is an add-on module for MRS. When enabled, the MRS API response includes a subscription object for matched merchants, indicating whether a transaction is a subscription payment and providing a confident score.

It uses the same MRS call, with no separete integration. Existing response fields are unchanged.

Availability: enabled per customer. Contact your Snowdrop account manager.

Request fields

In addition to the merchant name and country already sent to MRS, include the following fields with each transaction to enable accurate scoring:

Field
Type
Required
Description

amount

number (numeric string accepted, e.g. "5.99")

Yes

Transaction amount.

currency

string, ISO 4217 (e.g. EUR)

Yes

Transaction currency.

timestamp

string, ISO 8601 (e.g. 2026-10-20T14:32:00Z)

No

Transaction date and time. Use for batch requests. Defaults to the time MRS receives the request.

credit_debit_indicator

string: debit or credit

No

Only debits are evaluated. Credits (e.g. refunds) return matched: false. Defaults to debit.

Response structure

"subscription": {
  "matched": true,
  "score": 0.7
}
Field
Type
Description

subscription

object

Returned when MRS can evaluate the merchant.

subscription.matched

boolean

true when score is ≥ 0.7 (recommended threshold); false otherwise

subscription.score

number (0–1)

Confidence that the transaction is a subscription. 1 = certain.

You can use matched for the recommended threshold or evaluate the score directly to set stricter or lower thresholds:

Confidence levels

Confidence
Score

Strong

≥ 0.8

Probable

≥ 0.5 and < 0.8

Possible

≥ 0.25 and < 0.5

Weak

< 0.25

How detection works

Each merchant has a subscription profile:

  • Always: subscription-only brands (e.g. Netflix). Returns matched: true, score: 1.

  • Never: brands that do not sell subscriptions (e.g. IKEA). Returns matched: false.

  • Conditional: brands that sell both (e.g. Amazon). MRS looks for subscription terms in the merchant name and compares the amount with the brand's subscription prices in the transaction currency. A subscription term in the name is required for a match, and a matching price raises the confidence.

Examples

  • Always-subscription merchant:

  • Conditional merchant (subscription term found, amount does not match a known price):

  • Never-subscription merchant:

  • No subscription profile / module disabled: the subscription object is omitted entirely.

Notes

  • Single transaction: each transaction is evaluated on its own. MRS does not track payment history, detect recurrence over time, or predict upcoming payment dates.

  • Currency handling: amounts are compared in the transaction currency only, with no currency conversion performed. Always send the currency alongside the amount.

Last updated

Was this helpful?