RegTech and Compliance · 12 June 2026 · 6 min read
Evidencing Card-Not-Present Purchases in a Source-of-Funds File
Online purchases produce merchant records, card statements, and dispatch confirmations. A documentation file links the three so the spend pattern is reviewable.

Card-not-present purchases are common in a personal source-of-funds review because the spend pattern is one of the indirect indicators a counterparty uses to test the consistency of the customer's stated life with the account activity on file. The evidence base is broader than a single statement line.
The card statement records the merchant descriptor, the amount, and the posting date. The merchant descriptor is the acquirer's label and may differ from the trading name the customer remembers, so the documentation file records both the descriptor and the merchant identity once it has been confirmed against an order confirmation or invoice.
Order confirmations and invoices are the merchant-side record of the same transaction. They name the customer, the goods or services, and the delivery destination, and they tie the spend to a stated purpose rather than leaving it as a line on a card statement that could mean many different things.
Dispatch and delivery confirmations close the loop for physical goods. A tracking number, a carrier confirmation, or a signed delivery slip ties the spend to an address, which in turn ties the spend to a stated residence pattern. The file records each step so the linkage is reviewable rather than asserted.

Refunds and chargebacks are recorded against the original purchase line, not as standalone entries. A reviewer reading the file should be able to see that a given purchase was later reversed, partially refunded, or disputed, without re-deriving the relationship from two unconnected lines in the statement series.
Recurring subscriptions deserve their own treatment. A monthly digital subscription appears as a regular small line for months or years, and the file records the start date, the merchant, the service description, and the cancellation date where applicable, so the recurring pattern is explained rather than left as a series of identical lines.
Where the merchant is overseas, the file records the originating currency, the conversion rate the issuer applied, and any cross-border fee. Cross-border CNP purchases are sometimes flagged in counterparty review, and a file that pre-empts the question with documented detail moves the review forward.
Our scope is structuring records the client provides. We do not contact merchants on the client's behalf without written authority, do not represent the client in dispute proceedings with the issuer, and do not opine on the appropriateness of any spend. The deliverable is a documented purchase trail aligned to the source-of-funds file.
More in RegTech and Compliance
- Structuring a Source-of-Funds File Counterparties Will Actually Read
29 Jan 2026
- UK Record-Keeping Obligations: A Practical Reading
25 Feb 2026
- Scope Letters and Why Engagement Boundaries Are Written Down
27 Mar 2026
- Travel Rule Data Fields and What They Add to a Documentation File
14 May 2026
- Politically Exposed Persons Screening: What the File Records
28 Apr 2026
- Reviewing a Documentation File on a Tablet or Mobile Device
2 Jul 2026
- Third-Party Signatories Inside a Documentation Engagement
12 Jul 2026
- What Record Reconstruction Can and Cannot Prove
29 Apr 2026
- Inheritance and Deceased Holder Records in Digital Asset Files
8 Jul 2026
- The Regulatory Perimeter Around Documentation and Record Review
16 Sept 2026
- The Scope Letter as the Spine of a Documentation Engagement
4 Nov 2026