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
- 5b8e04b52f9f73ed67f81d4dcf639d6ecb6f6de9c2b0712119700aead4c72a1a
- request
- 3be4642d853a6429c0b63e2870ac9addfbaf1192a2eb1eafb0ec248671c734ab
- transaction
- 3d46f2ce4742f7634f39a35ee279b1cfaf6d06d7c7697398763db6fed65304e7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71653
the chainentry 71653
- sealed to the entry before
- 35ea02c5b761d276152f99a721dd4d796b9de2f5be932fe7c4474243253a86d9
- this leaf
- 2e53669ef4ef05fb6e6f08f43448af95cf66335a61aa0470226ed9015332c52e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6nehYRF539VU+L4mIe38lYvZof7/OS1ebUQ/c/bA8snkAatIm8WwzJGzCtRzoRyitOBfCbOV3CvRxaKyYXmwBw==