Verify the statement boundary
Confirm the suffix, closing date, due date, and whether you are viewing an issued statement or live activity.
A payment made after cutoff may belong to the following cycle even when current activity already shows it.
Open a missing-payment case
Put sender and card evidence on one timeline.
Card scope
Suffix, cycle, due date, and live-view time.
Payment
Amount, source, initiation, settlement, and confirmation.
Route
Payee, destination, and replacement-card history.
Issuer
Official contact, case, trace, and response.
Closure
Posting, fees, correction, and retained proof.
Collect sender evidence
Record source account, initiated and settled dates, amount, method, confirmation, and recipient identity.
Confirm whether the debit is final, pending, reversed, or returned. A temporary source-account reduction may not mean delivery.
Check the route
Compare payee, card suffix, bill-pay profile, and issuer instructions. Replacement cards and duplicate profiles can cause confusion.
Avoid sending a second payment as a test until you understand duplicate-payment risk.
Request a trace
Contact the issuer through the number on the card or its official site and provide only necessary confirmation details.
Record the agent, time, case number, expected action, and secure document request.
Reconcile the outcome
When the payment appears, compare effective date, credited amount, fee or interest effect, and available credit.
If charges resulted from the delay, preserve the timeline and request review under the issuer's process.
Start by proving the boundary: card suffix, issued cycle, closing date, due date, and observation time for any live account view. A payment made after statement close can be absent from the PDF yet visible in current activity. Keep the fixed statement and changing screen separate before calling the payment missing or sending another payment that could create a duplicate.
Collect source-side evidence: funding account, amount, initiation time, settlement state, payee, destination suffix, method, confirmation, and any reversal. A pending debit is not proof of completed delivery. Recently replaced cards, duplicate bill-pay profiles, mistyped payees, insufficient funds, and returned payments can interrupt different parts of the route and require different evidence.
Create one timeline for scheduled, submitted, debited, received, posted, returned, and corrected states. Automatic payment being enabled does not prove it ran, and a confirmation page does not prove the issuer credited the account. Record the issuer's expected processing window and cutoff rules from an official source, including weekends and time zone where relevant.