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
- cd05a8fedeabde4762db3a18b1f1ee1c71739409dd3a7eea5b62d0d6e0a470a0
- request
- e8c096cfba4767b00a2d09ee9201681cc7cc01bf4ebe9e8ad1a53ae4a74f9161
- transaction
- d614b5e73910bec7cf7d30438bcd8635c9fe23e2c9f1db85f8201bda52ff74accomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58508
the chainentry 58508
- sealed to the entry before
- 0de60b1ad5bad278a4dffa057771ef6e36efdbb1007894bcda9ebc2542467833
- this leaf
- 6d46a146415288d8b705651f92234ab0bb3fe76627a09a4c8bc18d881198e0aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Mr3xwq9OFFK/mSlCmxbeT5ajmwG0u7E77nSMfcmMpq5dYDSerdFCdjeORcVMPQobciE6cMXF1hp6alDnk6hQBA==