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
- d981bf210c9e850a911f851994b28cac04ba5c5004b982c9d9effa9458b0db44
- request
- ad32be277dffd13e7c01fcd7596fb26e6499f076ef060df83afbdec705390f1a
- transaction
- af4f1993d5da9dffc47b14cd7513cb0f40b95640ae7d8f5af16512165f2154c1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60884
the chainentry 60884
- sealed to the entry before
- 7c91d5651ae90a1ed50700fc201d420b657687cfb37d02ac36f237f2431b03a5
- this leaf
- bc3e88556a6621a0c135ffb1de1109212b9987a3c2e20358bc81cc6956e4e60c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c+qVcyPSuf+fHdAwV320cQQEzz0Aq+CJVXUXGIRHvVsLGWiyJmOqulcmp4uqqe23yfkc9K+mf6ANzBhAJBH4DA==