Customer transactions

A transaction records a customer's purchase or payment operation within a project. Find the correct transaction before checking its state, payment method, and references. Customer transactions are separate from your InAppify service invoices and revenue settlements.

Dashboard path

Select the project and open Transactions. You can also review a specific customer's history through Customers → select the customer.

Confirm the project, customer identifier, app, and purchase before taking action; a customer may have several similar purchases.

Search and filters

Search by transaction number, payment reference, customer identifier, or store purchase reference. More filters narrows results by date range, app type, product type, gateway type, and trial/non-trial purchases. Status filters separate successful payments from other states.

If a purchase is missing, review active filters and the date range, or clear them. Absence from filtered search results does not prove that no payment occurred.

Understand the states

• Successful: the transaction is recorded as successful. Also review the customer's entitlement to confirm actual access.
• Unsuccessful: the transaction is recorded as unsuccessful; do not treat it as a completed purchase.
• Pending: InAppify has not recorded a final result; use payment inquiry when needed.
• Expired: the payment process deadline has elapsed. This is not the customer's subscription expiration.
• Mismatch: the transaction is recorded with a mismatch state. Review discrepancy details and investigate rather than assuming success.

Refunded is a separate transaction badge. Recording a refund does not convert the original successful payment to unsuccessful: the purchase and refund are distinct historical records.

Transaction details

Open Transaction details from the row's actions menu. Depending on the purchase, details include status, transaction number, app, purchased package, customer, bank/store references, gateway name, displayed card information, and amount variance.

An InAppify transaction number is not the same as a bank reference or store purchase token. Identify which reference you are providing to support. Missing fields have different meanings across payment methods.

Check the purchase currency and unit; do not interchange rial and toman. Do not expose sensitive card details or purchase tokens in public messages or screenshots.

What should I review in the details?

• Customer, app, and package: identify who made the purchase and what they purchased.
• Transaction number: identifies the purchase within InAppify.
• Bank or store reference: helps reconcile the purchase with the provider's result; it differs from the InAppify transaction number.
• Gateway and card information: help identify bank-payment routing; not every purchase has card information.
• Amount variance: review displayed discrepancies alongside the other purchase details.
• Refund details: show the refund amount, reason, recorded reference, and whether linked access was retained or revoked.

Recheck an unsuccessful transaction

If the customer reports a debit but the transaction is unsuccessful or pending, inquire about that purchase before asking them to pay again.

1. Find the purchase in Transactions by transaction number or customer identifier. Change or clear the status filter if only successful purchases are visible.
2. Open Transaction details from the row's actions menu and match the amount, customer, and purchase time.
3. Return to that row's actions menu and select Check again. The current interface shows this for non-successful states; trial transactions do not support payment inquiry.

4. Wait for the response. InAppify checks bank purchases with their gateway and Bazaar/Myket purchases with their store. This does not create a purchase or a new charge.
5. Review the resulting transaction state and customer entitlement. Successful verification also attempts to complete the linked entitlement grant; a success message does not replace checking actual customer access.

If inquiry fails, retain the error and transaction number and follow the inquiry troubleshooting guide. Rechecking is not a manual override that forces unsuccessful payments to succeed.

Refund a transaction from this page

The refund action requires a successful, non-trial transaction with a positive amount and no previous refund, plus the project's refund permission.

1. Select Refund transaction from the purchase's actions menu.

2. Enter the reason and an optional refund reference.
3. Choose whether to revoke or retain access linked to this purchase.

4. Review the purchase and select Confirm and record refund. The recorded amount is the full transaction amount; this form does not provide partial refunds.
5. After success, check the Refunded badge and open Transaction details to review the refund and entitlement-revocation outcome.

For Cafe Bazaar purchases, the refund is performed through Bazaar itself: InAppify sends the purchase's refund request to Bazaar, then records the refund internally after a successful response. This is not merely an internal bookkeeping note.

For bank payments and Myket, this action does not transfer funds: return funds through the appropriate process first, then record the outcome in InAppify. Coordinate refunds for funds handled through InAppify's gateway with support.

Refund recording does not remove the successful purchase or revoke all customer access. Read the full refund and entitlement guide before confirming; the current form provides no refund undo or edit action.

Choose the appropriate action

• The customer paid but the purchase is not successful: inquire and recheck the payment.
• Funds must be returned or have already been returned: identify the payment method and read refunds.
• Payment succeeded but access is missing: review the customer profile and product-entitlement configuration; do not charge the customer again.
• You need aggregate sales analysis: use charts and reports. Transactions help investigate individual purchases.

Prepare information for support

Provide the project, customer identifier, transaction number, purchase time, amount and currency, app and payment method, shareable reference, and latest inquiry result. Use a secure support channel for necessary details. API keys and gateway secrets are not needed to identify a transaction.