# 💸 Transactions

{% hint style="info" %}
The history of transactions can be tracked here.
{% endhint %}

{% hint style="info" %}
Now we have divided the transactions into 02 sections such as one time (Payments) and recurring (subscription).

Please refer to  following tab for more details.

[subscription.md](subscription.md "mention")
{% endhint %}

1. Now transactions can be searched using an email.

![](<../../.gitbook/assets/1 (48) (2).png>)

2\. Every transaction has a unique ID which is called a Transaction ID.

![](<../../.gitbook/assets/1 (49) (2).png>)

3\. Transaction account email address can be seen here.

![](<../../.gitbook/assets/1 (50).png>)

4\. Discord ID and Discord tag of a transaction can be found here

![](<../../.gitbook/assets/1 (52) (2).png>)

5\. The GB/ DATA purchased can be seen here&#x20;

![](<../../.gitbook/assets/1 (53) (2).png>)

6\. Price per gb/ data purchased will be here.

![](<../../.gitbook/assets/1 (54).png>)

7\. The purchased product will be here

![](<../../.gitbook/assets/1 (56).png>)

8\. The transaction type and status of the transaction can be seen here. Orders can have two main es: Completed and Incomplete.

{% content-ref url="../transaction-status.md" %}
[transaction-status.md](../transaction-status.md)
{% endcontent-ref %}

{% hint style="warning" %}
An order is incomplete if payment is received but the data has not been received by the user. This sometimes happens due to the upstream provider's API failing. In this case, we recommend you to go to the USERS tab and manually add data to their account.&#x20;
{% endhint %}

![](<../../.gitbook/assets/1 (57) (1).png>)

9\. The data of the transaction placed will be here

![](<../../.gitbook/assets/1 (59) (2).png>)

10\. The transaction can be filtered by the status and the date .&#x20;

{% hint style="success" %}
We always recommend keeping the status set to ALL
{% endhint %}

![](<../../.gitbook/assets/1 (61) (1).png>)