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
- da5a85fa1019ca74a8fa829abc7bc5d7058354b46d0b01e74aec7651eb101699
- request
- c195980210e0f840c3a6546c2f7d87551bdc9bcce80698e43572e7fadc61ded0
- transaction
- 8df2ad8877bc9b93be7e12e9ae53e5e29bbe7648bd7bb8c3b76e70cfe3272507computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13902
the chainentry 13902
- sealed to the entry before
- a8f91478acf872b7214492244d53b9002e7d1363bf3fe101438c0ede7438fc72
- this leaf
- 5ebfe1bba92be89e0516b74a4cffae8ebf650719955c993e96ec0e6e3b2736d1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B1Iv6v61Gt2d9BoukmGJC8R3vHCWjtHU9cDcTWc1JlwR5nvf1gbcZXj5vAkLOZ0Rvz8ZBWYIHT9szA84ZjybCg==