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
- 053c10cbff070370b7d6dc7c60915d5e7e250e2203677ad4ec101133730bd790
- request
- b6affd83023fedceebb827951964b280e7e583bb92f429396592ebb0d0fcc20d
- transaction
- 49ff4a3056b2b1c91c91c57d6a48dabad93d5d5b4267fd81ecc7d014f9e88815computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59659
the chainentry 59659
- sealed to the entry before
- 73781caacd843bcae0f6b404c730ee5e0c576991604a83c7647a027608055366
- this leaf
- 2bfbc7667da923865f8acc66c8a6649f57d6e80a7f428f7bf012281a8bd6800d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BBmo2g+gJsYtDrd7q8swPR0l/LDaZRvUIAQZ2QzYPSEQHTlM0ObqvVaGAY8a5aESEjKsmlcOVHwu5h1pO1bCCQ==