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
- a2d00da35a18709592e27e521dc045890fe2ad72d6b742791031de56c00e281a
- request
- e165ac0f0c88a401eb7387b19a8662ae8f3925ac5db5959ff783c5796fbd98f2
- transaction
- d3262f3a87ecfc3af20b598cc99a67925208b83542ee4ccddf2513a02761116acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60706
the chainentry 60706
- sealed to the entry before
- 3c0262fd07285948079cd798f9353e79718bd48c3d39c00e4b532fb7f080babc
- this leaf
- 7cb236f58a2ea05aa76c743804f206f986950e6cd603fccc1dfd21cfd6930af4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fiYiiahDYa2K1yLoD+wH7afw1v36RAmIZd4MjEz9msFOGskn9/MHmO9S6ZO828IBUC1n/hCU8b03XKXh9rAmBg==