Getme Payments transactions
Review payment statuses, refunds, disputes, fees, and balance context without overclaiming provider behavior.
Getme Payments transaction records should be used as operational context for Stripe-backed payment workflows. A transaction can include authorization, capture, settlement, refund, dispute, fee, transfer, payout, or balance events depending on the payment method, charge type, account status, currency, and provider processing state.
What a transaction record can include
- Payment status and whether the payment was authorized, captured, failed, refunded, or disputed.
- Refund or partial-refund context, including pending states when the responsible balance has insufficient funds.
- Dispute or chargeback context, including evidence deadlines and balance impact where applicable.
- Currency and FX context when presentment currency, settlement currency, or refund/dispute timing differs.
- Fee and balance records that may require source-date review before customer-facing publication.
Transaction fields to review
| Transaction field | What it means | Status |
|---|---|---|
| Payment status | Shows the payment lifecycle state, such as authorized, captured, failed, refunded, partially refunded, or disputed where the workflow supports that state. | source-backed, workflow-dependent |
| Charge type | Connect charge type affects which balance is debited for refunds, disputes, fees, and negative-balance recovery. | source-backed, implementation-dependent |
| Refunds | Refund handling depends on charge type, available balance, account status, and whether the refund is full or partial. | source-backed, charge-type-dependent |
| Partial refunds | Partial refunds can require proportional or manual review for transfer, application-fee, tax, and balance effects. | source-backed, amount-dependent |
| Disputes and chargebacks | Disputes can withdraw disputed funds and fees, require evidence, and depend on charge type, connected-account status, and provider review. | source-backed, charge-type/account-dependent |
| FX on refunds or disputes | Currency-converted refunds or disputes can use the current exchange rate, so balance impact may differ from the original converted amount. | source-backed, currency-dependent |
| Fees and reporting categories | Fees, refunds, failed refunds, dispute reversals, and platform earnings can appear as separate balance/reporting categories. | source-check-needed |
Before telling a customer what happened
- Check the payment status and payment method before describing the transaction outcome.
- Review charge type before saying which balance is responsible for a refund, dispute, or fee.
- Check whether a refund is pending because the responsible balance is not yet available.
- Review dispute deadlines and evidence status before promising an outcome.
- Use source-check-needed for specific fee, tax, FX, or timing statements until current provider sources and Getme configuration are confirmed.
Do not promise refund timing, dispute outcomes, fee refunds, exchange-rate treatment, or merchant-balance recovery. These can vary by charge type, account configuration, country, currency, payment method, balance state, and provider review.