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
- 10859cf1d61c4f02bbbd989cd3970a645d3198653476e997497bb4315dfcd5d5
- request
- e042235262bd7a0dd57462778b88096cb89bda6996adcd4fce054ee53a39ee8a
- transaction
- 7034b7c2cad6d077e0c77659f6065913944fee635d7e3517ebf20cf5363c5015computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40380
the chainentry 40380
- sealed to the entry before
- 6d167755e7ce0284f1740ba5c4f9ff58a82deaf20bf72010cf352898bc9ca157
- this leaf
- 06bbb6e6878aaac1eb7f0982ce7129225fe00d6267e1bd86b5fe4c8256b95871
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 30xAWYCH3QttWDevzlGWkeONb7AH8hNKew4tGZbLokP+gn0E2JSfqfyDACY5AFrm8m1cVNrak2PJrSdaZXk/Ag==