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
- 993b20db41c17bce9c64db276d49565ee5a53026b072f524503eb49bd948421e
- request
- 18bf3be985eff56bd95d63a594be03df94bac4f6ee45489f0cea380e1f8ef449
- transaction
- f0df52fa843095f2cbb6763be4e835a7820e904faecfed22b2a3b26b2b39653ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43488
the chainentry 43488
- sealed to the entry before
- 4ffd4f4f94bb16046126ac9084a231b9d67cd0598314e8a157c9b603d760c42c
- this leaf
- c44626072fa0a74732a334fcf91c4f9a8e8e83855b5fc17b5b78db778f0f8c47
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 75qpOzaDNkPhrjOp9eqGTpR34I8Zoj6BVj/iiQnFwB6IXBsQsVMfShusD70V6o0LLBuVP7VVL+RXK6alHGCeDQ==