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
- 69642c97172e9f3770dc311bb7298b1c1f431225cd7336e5eb2b9bf1289518ad
- request
- 05af430e1b584756950c7068845563410fb821fc14bad03ca04d2f7f5007a13a
- transaction
- cff9196fd7932de976dead56e3e807c47c81a882dc1dd02416888c6dac6e3c7ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54297
the chainentry 54297
- sealed to the entry before
- bf29082229afdeecb2feb9f18478920e45534870c5e3c372c776d69aad2b4823
- this leaf
- 24bca001842026579799d38eb8749235e388d7bfff7fc0030a109bd48a38f7ee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H/gyXKSdoTOT1qfIsX2py3xOTJNWqaOwANoCK4ayTBmsCDwXKzFcnMkm0Jp6wKTXD9zOm30r5zm9QUVUdAPFAQ==