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
- c6a0a67925f29b6835b3efa0ff09ce1200bb7f0501de9c18315c9a65e35e37c5
- request
- 7ea257f853f00bf221c2b20a2e06cf5df0e4d8e4bb025554297a80c92db5c151
- transaction
- 36ce08955c9e041fbaa4120542ae32eb4eb81a17a29f50dea9077d295185e079computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28300
the chainentry 28300
- sealed to the entry before
- 7ef9f5027c57d26832912613ca777bdd219361918ed7544a64a40b8351ad4bc9
- this leaf
- eece05e92de8a13236f87c6caf16a5c86adc2d0b74a79e7aeec957e07f2be108
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tVwCg3We0bIzJW9osEUsnKlyeRaLbvzANrbTOME05sPvcvly4Mrq1oA/BaJl1mqIHJ9G1TfJ/UunxHPLCtC8BA==