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
- 7cc487a3f3715c38a6432d267eea6cd51aa3161c933fe0bb346db2f8f54f52e3
- request
- 66d8d0daad3c2a37ecaff302f04c7f8552bf6dd67cdbc0604b38d58f4c361cb4
- transaction
- f75b6c0453c18581a608732f0abb302b887b22cd1b9822c614ba180334ff1d81computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1300
the chainentry 1300
- sealed to the entry before
- 72757712bc9f984ee8033d6610605a0c9debf155085dd0abd4fc93a44ffe1a20
- this leaf
- 8af0241bd9df47045712ff5a825bb0f6438c69e2ad253cd06681df7b52dd5b93
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- M/Cq4x0wFb0pPQ0jp666KaUeiBnkQ3iLFLBNswTp9LBikXWyMIDTo1UShEv57tN5589/UhiQwSvFO+7kTUgSBw==