> For the complete documentation index, see [llms.txt](https://docs.devtodev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devtodev.com/integration/autocapture/automatic-payment-tracking.md).

# Automatic payment tracking

Devtodev allows you to collect payment and subscription information automatically for the Google Play and App Store platforms. All you need to do is enable the corresponding module during the SDK initialization and configure store setting in the devtodev interface. 

The automatic payment tracking system will help you avoid integration errors with data submitted using the [Real Payment](/integration/integration-of-sdk-v2/setting-up-events/basic-methods.md#real-payment) and [Subscription](/integration/integration-of-sdk-v2/setting-up-events/basic-methods.md#subscriptions) events. This system will also help you avoid sending fraudulent transaction data, as each transaction is additionally verified on the Google Play and App Store platforms before being recorded in the database. 

{% hint style="warning" %}
**Important**: Automatic payment tracking is only available for the Google Play and App Store platforms, and only if you are using their native payment systems. \
If you are using a third-party payment system, you will need to integrate the [Real Payment](/integration/integration-of-sdk-v2/setting-up-events/basic-methods.md#real-payment) Basic event. 
{% endhint %}

{% hint style="info" %}
Please note that you should not simultaneously use an automatic payment tracking system and send payment data using the integrated [Real Payment](/integration/integration-of-sdk-v2/setting-up-events/basic-methods.md#real-payment) and [Subscription](/integration/integration-of-sdk-v2/setting-up-events/basic-methods.md#subscriptions) events, as this may result in duplicate payment data. \
Devtodev will do its best to prevent including such duplicates in the statistics; however, for some integration cases, this is impossible (e.g. when using *Google Play Purchase Token* instead of *Transaction ID* in Real Payment event data). \
Therefore, when you switch to automatic payment tracking, we recommend that you remove the integration of [Real payment](/integration/integration-of-sdk-v2/setting-up-events/basic-methods.md#real-payment) and [Subscription](/integration/integration-of-sdk-v2/setting-up-events/basic-methods.md#subscriptions) events, except in the case of tracking transactions with third-party payment systems.
{% endhint %}

{% hint style="warning" %}
While automatic payment tracking helps avoid fraudulent transaction data, this mechanism **does not automatically mark users with such payments as cheaters**. In case you would like to mark users as cheaters, use a [dedicated method](/integration/integration-of-sdk-v2/setting-up-events/user-profile.md#cheater) or [flag the User card](/reports-and-functionality/project-related-reports-and-fuctionality/users.md#mark-as-cheater-or-tester).
{% endhint %}

{% content-ref url="/pages/JSTvq6SDrJt7h9ocqtwk" %}
[App Store](/integration/autocapture/automatic-payment-tracking/app-store.md)
{% endcontent-ref %}

{% content-ref url="/pages/Qp0MFkkMwNNxUoVJ2e9Y" %}
[Google Play](/integration/autocapture/automatic-payment-tracking/google-play.md)
{% endcontent-ref %}

{% content-ref url="/pages/LHz5EuRgatEcP0d1Ltjf" %}
[Aghanim](/integration/autocapture/automatic-payment-tracking/aghanim.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.devtodev.com/integration/autocapture/automatic-payment-tracking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.