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
- 92da17ecc5efb649d9f1e226448f80394229a36c5fda89c02170d46c7f3fc482
- request
- a113f54dcbeb43e3304c767af7486cffee0b95b0f4387bbe1a14bdeb52473e69
- transaction
- 315216414414208c4a401a425a50bca63fc08ae4b419c292d6c572a498c3bdb4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70784
the chainentry 70784
- sealed to the entry before
- d9337bd6c65f84dc4a5bd202d23552b14ecd60745ebe0cadb5f6a3092a3e6278
- this leaf
- 4add28c983f901339f3338041c7a162e3903b3acdcf1ccfe008832318eae3d15
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QeBAiDffoIvsLihY3eZ99r5YKJ2sEVJ7FHge5DuL91sxKP9T1HNIak1RbQXk+z8+Q0bAGtiv6/YO/3GK1092Aw==