Guru's Verification engine ensures consistency, confidence, and trust in the knowledge your organization shares. Learn more.

Report: Transaction data

This report contains all data about the Transactions that are done through the Magine Pro Platform, either through Adyen or Stripe. This report does not include any refunds or similar, that information can only be found in the systems of Adyen or Stripe.

Each date will get a new report. A report for one day can be updated during the following 15 days after it was created because a transaction can remain as "pending" for up to 14 days before it's marked as "failed" if no notifications have been received from Adyen or Stripe.

Columns

All timestamps in this report are in UTC.

  • user_id - The unique ID of the user for whom the transaction was made.
  • transaction_id - The unique ID for this transaction. The ID can also be found in Adyen to see the transaction on Adyens side.
  • transaction_timestamp - The timestamp of when the transaction was initiated.
  • transaction_status - Status of the transaction. The possible transaction_status'es are: success, failed, pending.
  • transaction_type - Indicates if this is the first time the card is being used or if it had been registered already. The possible transaction_type's are: registration, recurring, subscription_upgrade.
  • transaction_payment_method - The payment method that was used for this transaction. E.g. adyen:credit_card.
  • transaction_currency - The currency for the transaction.
  • transaction_gross_price - The full price of the transaction before any applied discounts. The price is in the sub currency. E.g. If the gross price is €4.99, the value in this column would be 499.
  • transaction_net_price - The price of the transaction that is actually charged from the user with applied discounts. The price is in the sub currency. E.g. If the net price is €1.99, the value in this column would be 199.
  • transaction_from - Timestamp for when the transaction is valid from. E.g. If the Subscription of the user was supposed to be renewed at one date, but the payment did not go through until a couple of days later, this date will still be for when the Subscription was first meant to be renewed.
  • transaction_to - Timestamp for how long this transaction covers. I.e. for offers of type: Subscription, this is the date when the user will be billed the next time.
  • offer_id - The unique ID of the Offer that was paid for in this transaction.
  • transaction_promocode - Promocode that was used for this transaction to give a discount
    • Corner cases:
      • Question: Why can I find a user that have a promocode in this report but I can't see that promocode in Console (or in the promotions data report)?
        • Answer: When a user have used a promocode for a transaction that have failed or are currently pending, the promocode have not been fully consumed.
      • Question: Why can I see on a user in Console (or in the promotions data report) a promocode that I can not find on any transaction for that user?
        • Answer: This will be the case when a user have added a promocode to an active subscription and then either canceled the subscription before the next renewal or that the next renewal have not yet happened.
  • transaction_original_offer_id - For a transaction with "transaction_status: subscription_upgrade", this column will be populated with the offer_id that the user had before they did the upgrade.
  • transaction_refund_amount - For a transaction with "transaction_status: subscription_upgrade", this amount will be what have been deducted from the price of the new Offer depending on how many days was left on the original subscription

You must have Author or Collection Owner permission to create Guru Cards. Contact your team's Guru admins to use this template.