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
- 9749e7f734e3ea4e7f95e5a15f4929d9329e72cc8edf0c2853e8393affd7aa90
- request
- 2d28aedd9017a76014a65f2a12ad28cf4d8e74386b47e78abc0d3382f663c597
- transaction
- 96a2d00dadf3794446d9232365312a691805b39fb1da83a5d192e6807ad6da96computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66074
the chainentry 66074
- sealed to the entry before
- 553d4e807f4dacd78e287e6f31411eabe05df9880b485f39ed16f21aa963e4ce
- this leaf
- 873449aab4591423d4284c23bfa04ff858795c3560a6b4227432fd39620759f5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hEXEEaDN/ub/oD3CrNpJ5p8PK6hEJgPHdsAkiihfiqnaXEvKM7x5Yeg6imZFkemqrt0HlbrAEQc3p20ARv0BCg==