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
- 02658e103c7daecbcc6e9a1c65f417ad3267a10bdd753ba235aed6c2674f0f5e
- request
- 6db53b02c82041918ee123364a668f6c892d6ff5ebe175471cf0848d7bd153a2
- transaction
- 6eca31986987927b27daeb6599faf783f60608570650becd2cc1192bb0c87ff9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 121
the chainentry 121
- sealed to the entry before
- 24e0b185436318c1cb4ebde41994f62562ed2134f8241691f5b407a8043c490d
- this leaf
- 3aef21e1d2bc9a22573b2b5804bd0777b666a2f70d439d2b0fc9bd8dc2925320
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 32fk92gjn2vgmVVw97Ia+IHoAXaooIkfEJ/Hh4YAWaAcx/FlR+9591uXFmiPevVzpZ2TT8SEBsRp4nhukLlhDQ==