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
- c5a37075deb9637ce543855c4620268b3f1473d4ed62b9b329b0f0c120ad2829
- request
- fa1944695007a69268459e4c9a409919a4c96fe51863370f6592d92a0036bc4a
- transaction
- d3f04b7dde70078d8d1b4ebafaf0df97eeaad41b50ae65c5aa051ce02e24a602computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43766
the chainentry 43766
- sealed to the entry before
- 1718283ceed6f1a8d962ba3cb315f6abd57143e1329c64097b0dcd877d93ae38
- this leaf
- 2d5e4d434697f355483a40ab92d6bca407995982ab84575439db83c65adfce65
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Jp8c6KDn1GhpXKaA33foXI2XLDDeWmC2D/xEWUL0mzHrSmi1J6HjEwV7L6vW/B2O8HPnAYYW3SvgzTIW+aYvDQ==