Every payment in FeitPay has a timeline. Read top to bottom, it tells the full story with the evidence attached.
The entries
- Payment intent created — your server asked for an amount in a currency.
- Invoice opened — the customer opened the checkout and FeitPay opened an invoice in its Bitcart account: for each asset offered, the exact amount, the exchange rate Bitcart used and the address to pay, valid until the invoice expires.
- Payment detected — Bitcart saw the transfer. The transaction hash and the amount sent are recorded.
- Confirming — the transfer has its first confirmation but has not yet met the store’s confirmation policy.
- Confirmed — Bitcart reports the invoice complete. This is the moment to fulfil.
- Balance credited — whether the amount received has been credited to your custodial balance. It is credited exactly once.
- Webhook deliveries — each attempt with its response code and timing.
- Billing — the platform fee accrued for this payment, invoiced separately.
When something looks off
- Underpaid: compare the invoice amount with what was sent. The customer may have paid network fees out of the amount.
- Late payment: funds that arrive after the invoice expired are held for review. An operator verifies them before they are credited to your balance.
- Manual review: Bitcart reported the invoice invalid or refunded, or a status FeitPay does not recognise. The payment waits for a person, never for a timer.
- Webhook failures: the delivery list shows your endpoint’s response codes. Fix the endpoint, then replay the delivery — the event ID stays the same, so deduplication keeps you safe.
Exporting
Timelines and payments can be exported as CSV with UTC timestamps for reconciliation, so your finance team works from the same evidence as support.