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
- 20cfb09c9bf4d4b47888b29a9d10f4839c684c174810fb9497d24d4e9bddb2bd
- request
- 84bc823dcedf8b2b9a8fbdfdcee1ddb644f5f3b5e2f0fcbeebc3e9f2a23aa53c
- transaction
- 1e501770c57d1cd32c0de3707dc22683613a6b3319bb4ad49ddfdae9353784f9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36440
the chainentry 36440
- sealed to the entry before
- c564511738962317a1c2609a2326c72647b46f7defaffcdd8dbce475c4aa68e4
- this leaf
- bba8895eaed6dc5aeee12b4048a612f24a9de79c6b77d18a98fd69e424079d5e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U/V+MLNz7XPKKX/P6fxwUJ9Df+9r6jhKFXyOboj4Kl6sbg5po/A5BdHBnfqskQ6AAOaron5vonFSq8+1TliOCw==