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
- a26fa681f0b1d5f7eddec10143c6f2c3767076a80bc61f0ff21ee054b8a420e4
- request
- 7a8bcf86521203ffb1f440fd35d06214205b23fe025f0ac81acea763d3db420c
- transaction
- d44c18146735fd0888ac0561858a03f53628e226fe9b9575286cedaa2b35aef2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52989
the chainentry 52989
- sealed to the entry before
- 16481c1212a37c87abc68070dad2eb91971432d686c00e11e5181b731e84bd26
- this leaf
- f07760f22907c61015edec6baebb4de8e2dee50c7ec2c4e918a224a2eab361a0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lEiOSryRaTb4KytW4NCCxcTG4NDnJYXj9TwgxyLTctgYyn3T/M4anlzdolllIXjdEIsuBN8gg2+Ub2hsYU8MCA==