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
- 1d62a0179f194a31efa588d59dae5bcee2d33f24b01030dcaf562b3bcffbc02d
- request
- da1a7ef7179163d8a59e9b6db3211efc6b1855a857f4b38745012b6f333d2219
- transaction
- 7e1cea9ad0593d2a8432649ed4952bfca96525996b6ba5045aad58a9f5cd7e73computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1470
the chainentry 1470
- sealed to the entry before
- 85495fe93fa010342ead6bda9aa907cc1a3809b271c9ff2d2f2f0449764753cb
- this leaf
- ee167ba65f2e8981130db05af8784a0185a4218801d55b6703b68fd391025d1c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YkGMLUf860px5CnFAzTLeI02xx/HGA0T0NTNoUXmFSR6XZOltwUDwbsecqTJ7POU905rQcCF5qzCeVlpn6tpDA==