why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 5c41793e9aa15c703da3ac75c763cfbe8ae6771b9d670635d55d0cec18592230
- request
- 1019a1d25cf876d08fd3dc0669ba03d2165994605bf220f1377cd80b3068bdf5
- transaction
- 295382fa13052e0e7e6f45f6d0968eef283eff05dd6a6b0f4a4752c10c23ac31computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65444
the chainentry 65444
- sealed to the entry before
- d598992f2a58664caf5e008e3fb9b72410b9b9c9fb9e9148b058faa3693a6803
- this leaf
- 2034fb281eb2521fa80cd6a8eacf89fd0e410c2a38734877e01be2490ee1e622
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MvnLgM+bMLz30Ub4yXLw9vyqWdgdnecqK9eIqM3IeMW+wUe67p/KB7Z/Kq4sQ5AEsvAA/VpsMTHoC24tCSKSAg==