Digistore24 Webhook MCP Server

Digistore24 Webhook

Digistore24 IPN posts order, subscription, refund, and ancillary events as urlencoded form fields. Storage normalizes each POST to flat JSON in export.json. Each delivery is one IPN call (one event, often one transaction). Tools read what already landed — there is no pull API and no way to acknowledge, refund, or replay IPN from here.

First moves

1. Latest report — default for “what order or event arrived last”.
2. Read export.json.event — classify the notification before interpreting amounts or access.
3. Recent reports — compare order_id, payment_id, and transaction_id when deduping retries.
4. One report by id — after listing, when the user names a specific delivery.

Event types (event)

Each IPN sends exactly one event. event_label mirrors the backoffice name when present.

Order lifecycle

Other IPN types

Lifecycle distinctions

• on_rebill_cancelled — cancellation recorded; access may still be valid until the paid period ends.
• on_payment_missed — billing date passed without payment; use for temporary suspension, not final cancellation.
• last_paid_day — paid period over; use for permanent access removal. Also follows failed retries after on_payment_missed.

Stable order-event fields (when present)

Inspect export.json — optional blocks depend on product setup (addons, licenses, coupons, rebilling, upgrades).

Event and mode

• event, event_label — notification type
• ipn_version — IPN interface version
• api_mode — live or test

Order and transaction ids

• order_id — stable across transactions on the same order
• payment_id — unique per payment on an order
• transaction_id — transaction record id
• transaction_type — payment, refund, or chargeback
• transaction_amount, transaction_currency, transaction_processed_at
• order_date, order_time, order_date_time, transaction_date
• order_type — e.g. regular, upgrade, phone_order, cart, vat_change

Product and amounts

• product_id, product_name, product_language, product_delivery_type (digital or shipping)
• variant_id, variant_name, quantity
• product_id_2, product_id_3, … — addon products on the same purchase
• currency, amount_brutto, amount_netto, amount_vat, vat_rate
• amount_vendor, amount_affiliate, amount_payout, amount_provider, amount_fee
• pay_method — e.g. PayPal, credit card, ELV

Buyer

• email, buyer_id, language, country, is_gdpr_country
• address_first_name, address_last_name, address_street, address_city, address_zipcode, address_country, address_company, address_phone_no

Billing model

• billing_type — single_payment, subscription, or installment
• billing_status — paying, aborted, unpaid, reminding, or completed
• pay_sequence_no — 0 for single payments; 1, 2, 3… for installment/subscription cycles
• number_of_installments
• is_cancelled_for — access should end on this date when set
• billing_stop_reason — e.g. by_operator, by_buyer, by_refund, by_chargeback, by_payment_denial

Affiliate and tracking

• affiliate_id (0 if none), affiliate_name, campaignkey, trackingkey
• salesteam_id, salesteam_name
• custom — vendor-defined passthrough from the order form
• merchant_id, merchant_name

Rebilling extras (subscription/installment)

• first_amount, first_vat_amount, other_amounts, other_vat_amounts
• first_billing_interval, other_billing_intervals
• next_payment_at, rebill_stop_noted_at

Upgrade extras

• upgrade_type, upgraded_order_id, upgraded_product_id, delivery_date, upgraded_order_paid_until

Optional product-delivery blocks

• License: license_id, license_key, license_key_type; suffix _2, _3 for addons
• Coupon purchase/use: coupon_code, coupon_id, used_coupon_code, used_coupon_id
• E-ticket on order IPN: eticket_date, eticket_hint, eticket_url (suffix variants for multiple tickets/products)
• Newsletter: newsletter_choice (none, optin, optout), newsletter_choice_msg

Integrity

• sha_sign — upstream SHA-512 signature over other parameters (present on signed IPN calls)

Non-order event fields

• on_affiliation — email, affiliate_name, affiliate_link, referring_affiliate_name, product_id, product_name; order_id is affiliate-<id>
• eticket — eticket_id, eticket_code, eticket_no, eticket_count, eticket_is_blocked, action, order_is_paid, order_billing_status, participant address_*, location_*
• customform — form_no, form_count, dynamic data-XXXXX keys per form field
• connection_test — merchant_id, merchant_name, product_ids

Gotchas

• Read-only — cannot acknowledge, refund, cancel rebilling, or replay IPN from here.
• One event per POST — filter history by event plus id fields, not filename alone.
• Retries and duplicates — Digistore24 retries failed deliveries and may resend after manual order fixes; compare payment_id / transaction_id with source.captured_at.
• Multiple products — one order with several items can produce multiple IPN calls (one per transaction).
• Field presence varies — license, coupon, eticket, rebilling, and upgrade blocks appear only when configured for that product.
• UTF-8 — all upstream text is UTF-8; values may include line breaks when copied from docs.

Response shape

• export.json — flat IPN fields (preferred for order, event, and buyer questions).
• export.text — raw body when JSON is large or non-object.
• source.captured_at — when the POST landed here; compare to order_date_time or transaction_processed_at inside JSON for upstream timing.

Operational order

1. Start with the latest report — do not guess a report id.
2. Read export.json.event before quoting amounts or access state.
3. If captured_at is older than expected, say so — IPN fires when orders and subscription events happen upstream.
4. List recent reports only for history, duplicate suspicion, or explicit compare-by-date asks.
5. Read ## This connection in the skill supplement for product- or funnel-specific field notes.