Subscriptions

Subscriptions & Recurring Payments protects MRR: recovering failed charges, managing the card lifecycle, and predicting churn before it happens. This page lists the 42 data points Athia uses for this use case, with their definitions, sources, availability and data class.

Field names below are the payments-standard names for each data point, so use this page to line your own schema up against them.

📘

The field names on this page are payments-standard names — they describe each data point at the level of the standard it comes from. Athia Data Dictionary carries the names Athia uses and a crosswalk between the two. You do not have to match either exactly — the mapping from your own columns is agreed with your Athia team on ingest. One delivered field often covers several data points here, decline codes especially.

Sub-use cases

  • Involuntary churn / dunning — failed recurring charges, retry sequencing and decline reasons that put an active subscription at risk.
  • Failed-payment recovery channels — which retry, dunning stage or fallback method actually recovered the invoice, and how much was recovered when.
  • Card lifecycle management — stored card expiry, network tokens, Account Updater events and fallback payment methods ahead of the next billing date.
  • MIT/CIT tagging — correct merchant- vs customer-initiated marking, credential-on-file flags, scheme transaction IDs and consent evidence.
  • SCA/3DS for recurring — the stored-credential attributes that determine exemption and authentication handling on recurring charges.
  • MRR/ARR/LTV cohorts — recurring revenue movements, plan and quantity changes, discounts, tax, proration and FX for cohort reporting.
  • Pricing & plan experiments — plan, plan-change and discount data behind upgrade, downgrade and pricing tests.
  • Lifecycle flows — subscription status and plan transitions across the customer lifecycle.
  • Trial→paid conversion — trial start and end dates and the status they convert into.
  • Voluntary churn prediction — customer-level signals for customers who choose to cancel.
  • Cross-border recurring — billing currency and FX conversion to the base currency.
  • Recurring chargebacks — the card and consent evidence needed to defend disputes on recurring charges.

Data points

All 42 fields, grouped by category.

Subscription core

FieldCategoryDefinitionTypeExampleSourceAvailabilityData class
subscription_idSubscription coreUnique identifier of the subscription.uuidsub_8a2…Merchant / ERP integrationFullNone
customer_idSubscription coreIdentifier of the subscribing customer.uuidcus_4f0…Merchant / ERP integrationFullPII
plan_idSubscription coreIdentifier of the priced plan/tier.stringplan_pro_monthlyMerchant / ERP integrationFullNone
statusSubscription coreSubscription lifecycle state.enumpast_dueMerchant / ERP integrationFullNone
billing_period_startSubscription coreStart of the current billing period.date2026-05-01Merchant / ERP integrationFullNone
billing_period_endSubscription coreEnd of the current billing period.date2026-05-31Merchant / ERP integrationFullNone
next_billing_dateSubscription coreDate the next charge is scheduled.date2026-06-01Merchant / ERP integrationFullNone
trial_start_dateSubscription coreTrial start date.date2026-05-01Merchant / ERP integrationFullNone
trial_end_dateSubscription coreTrial end / conversion date.date2026-05-15Merchant / ERP integrationFullNone
currencySubscription coreBilling currency.codeEURMerchant / ERP integrationFullNone

Billing events

FieldCategoryDefinitionTypeExampleSourceAvailabilityData class
invoice_idBilling eventsIdentifier of the invoice being charged.uuidinv_91c…Merchant / ERP integrationFullNone
attempt_idBilling eventsIdentifier of an individual charge attempt.uuidatt_22b…Merchant / ERP integrationFullNone
retry_attempt_numberBilling eventsSequence number of the dunning retry.integer3Merchant / ERP integrationPartialNone
decline_code_rawBilling eventsRaw processor/issuer decline code.codedo_not_honorPSP / processor reportFullNone
decline_code_canonicalBilling eventsNormalized canonical decline reason.enuminsufficient_fundsAthia derivedFullNone
dunning_stageBilling eventsCurrent stage in the dunning sequence.enumretry_2_emailMerchant / ERP integrationPartialNone
recovery_outcomeBilling eventsOutcome of the recovery attempt.enumrecoveredAthia derivedPartialNone
amount_recoveredBilling eventsAmount successfully recovered.money1999 EURMerchant / ERP integrationFullNone
recovery_timestampBilling eventsWhen recovery succeeded.timestamp2026-05-20T09:00ZMerchant / ERP integrationFullNone

Stored credential

FieldCategoryDefinitionTypeExampleSourceAvailabilityData class
mit_indicatorStored credentialMerchant-Initiated Transaction marker.booleantruePSP / processor reportPartialNone
cit_indicatorStored credentialCustomer-Initiated Transaction marker.booleanfalsePSP / processor reportPartialNone
mit_typeStored credentialMIT sub-type (recurring, installment, unscheduled).enumrecurringPSP / processor reportPartialNone
cof_indicatorStored credentialCredential-on-file flag (initial vs subsequent).enumsubsequentPSP / processor reportPartialNone
scheme_transaction_idStored credentialVisa TID / Mastercard Trace ID linking the credential chain.stringMCC1234567890PSP / processor reportLimitedNone
original_credential_capture_dateStored credentialWhen the credential was first stored with consent.date2025-11-02Merchant / ERP integrationLimitedNone
consent_proof_idStored credentialReference to stored consent evidence.uuidcns_77a…Merchant / ERP integrationLimitedSensitive

Card lifecycle

FieldCategoryDefinitionTypeExampleSourceAvailabilityData class
pan_last4Card lifecycleLast four digits of the card.string4242PSP / processor reportFullPCI
BINCard lifecycleBank Identification Number of the stored card.string424242PSP / processor reportFullPCI
card_expiryCard lifecycleStored card expiry (MM/YY).string08/27PSP / processor reportPartialPCI
network_token_idCard lifecycleNetwork token for the stored credential.stringtkn_5dF…PSP / processor reportLimitedPCI
network_token_statusCard lifecycleLifecycle status of the network token.enumactivePSP / processor reportLimitedNone
account_updater_eventCard lifecycleAccount Updater event (new PAN/expiry/closed).enumnew_panAcquirer / network fileLimitedPCI
au_event_dateCard lifecycleDate of the Account Updater event.date2026-05-10Acquirer / network fileLimitedNone
fallback_payment_method_idCard lifecycleAlternate PM to use on failure.uuidpm_back_3Merchant / ERP integrationPartialPCI

MRR movements

FieldCategoryDefinitionTypeExampleSourceAvailabilityData class
mrr_movement_typeMRR movementsType of MRR change.enumexpansionAthia derivedFullNone
mrr_deltaMRR movementsSigned change in MRR for the event.money+1000 EURAthia derivedFullNone
plan_change_eventMRR movementsPlan transition (upgrade/downgrade/etc.).enumupgradeMerchant / ERP integrationFullNone
quantityMRR movementsSeat/unit count on the subscription.integer25Merchant / ERP integrationFullNone
discount_amountMRR movementsApplied discount on the period.money200 EURMerchant / ERP integrationFullNone
tax_amountMRR movementsTax charged on the invoice.money380 EURMerchant / ERP integrationFullNone
proration_amountMRR movementsProration adjustment for mid-period changes.money-150 EURMerchant / ERP integrationFullNone
fx_rate_to_baseMRR movementsFX rate converting billing currency to base.decimal1.0850Third-party enrichmentFullNone

Availability

Availability describes how reliably Athia can obtain a field in practice, not how important it is. Fields marked Partial or Limited are still worth mapping — they simply need the right source or setup to arrive consistently.

ValueWhat it means
FullAthia gets this reliably from standard sources.
PartialAvailable from some providers, or some of the time.
LimitedAvailable only in specific setups or on request.
Not availableAthia cannot obtain this today.

Field-level definitions for the core entities are in Athia Data Dictionary.


Did this page help you?