--- title: Understanding transaction details description: Find the payment method, buyer information, fees and settlement status for a sale, and understand what pending means. --- Open your community's **Activity** page and select a purchase to see its details. The amount is shown in the currency the buyer paid. The transaction breakdown adds payment and settlement information as it becomes available. ## Payment method and buyer information The **Payment method** column shows how the buyer paid. When a method has a logo, hover over it to see its name. Stripe is the payment provider; card, BLIK or a wallet is the payment method. Insy keeps the available purchase information locally, including buyer contact and billing details, payment references and the actual method used. Card details are limited to information such as the brand and last four digits. Already captured buyer details are retained when payment data is refreshed. Some fields may be unavailable. A dash means that information has not been recorded, not that the amount is zero. Older Activity entries may lack payment details; the new presentation applies to new entries with a linked payment. ## Reading the breakdown | Field | What it means | | --- | --- | | Subtotal, discount and sales tax | Purchase amounts reported for the transaction, when available. | | Insy platform fee | The application fee collected by Insy through Stripe. Before synchronization, an estimate may use the rate saved with the payment. | | VAT included in platform fee | VAT already included in Insy's fee. Do not add it again. | | Affiliate commission | Recorded affiliate commission, including its amount, currency and status. No recorded commission means no commission record is available for that payment. | | Refunded | The recorded amount refunded to the buyer. | | Settlement fees | Total fees reported for the Stripe balance transaction. Do not add the separately displayed application fee to this total again. | | Net settlement | The net amount reported by Stripe, in the settlement currency. | | Buyer at purchase | Available buyer details retained with the purchase. | A purchase, an affiliate commission and a settlement can use different currencies. Compare amounts in the same currency; do not subtract a PLN fee directly from an EUR purchase amount. ## Why is Stripe settlement pending? **Pending availability** means the saved Stripe settlement is awaiting availability on the Stripe balance. The buyer's payment can already be completed successfully. **Expected availability** shows the date supplied by Stripe. Insy refreshes the settlement after that date, so the displayed status can lag behind Stripe. This date is not a promised bank payout date: bank payouts follow a separate schedule. > **Pending does not mean the buyer should pay again** > > Check the payment status first. A completed payment with a pending settlement does not need a > second payment from the buyer. ## Admin payment and merchant views These views are for authorized Insy administrators. Merchants use their own Activity and finance pages. The admin **Payments** page supports filters for currency, merchant, provider, actual payment method and affiliation. The dashboard's **ALL** currency view keeps totals separated by currency. In **Stripe Merchants**, the payment data sync section shows: - **Tracked**: eligible payments included in reporting. - **Synced**: payments with at least one successful data refresh; optional fields can still be absent. - **Awaiting first sync**: payments with no successful refresh yet, including those that encountered an error. - **Failed last attempt**: payments whose latest refresh failed, even if an older snapshot exists. - **Awaiting Stripe balance availability**: payments whose recorded settlement is pending. These counts overlap. A failed refresh can affect either a payment awaiting its first sync or one that was synced earlier. Pending balance availability is separate from a synchronization failure. The list and details refresh every 30 seconds. **Retry payment synchronization** queues eligible missing data and failed refreshes for that merchant. Processing happens automatically in batches, so results are not immediate. Previously recorded details remain available after a failed refresh. Historical payments outside reporting are not backfilled by this action. Refreshing the Stripe merchant account itself is a separate action. > **Two different kinds of retry** > > Retrying synchronization only retrieves payment information. To retry collecting a failed > subscription payment, configure [Stripe Smart Retries](/selling/smart-retries). The platform commission and VAT included in it. Configure Stripe to retry subscription payments.