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
- 0cf3021dbd11b8a9abd87a902eba00055b5a40625ae4fdaf7cc41b0022178aae
- request
- e2cb8c26885b7d36058c56dd61db3796581f0ef8df3d0009f0a1e0040ef22f05
- transaction
- 5779fd8cf7dd09a3269140e1e17f62873569d4dc73b1dfa71de77047e3a8fee0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51056
the chainentry 51056
- sealed to the entry before
- 91e2d7dab02d8fc70d4ed49b608d5d48f4c40da4c3744be1db5f458f2cd76e88
- this leaf
- 91a21241627652a0e7f1c51dafd1444e4915e3c9c81845322e4db344ed443d24
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rSYNlMCgp+m5RQwUrgxR4R7t83DAybLi6nO0r7Q1IDW3QScUkXSo016mUBp9U8yafsEsBva7QRDjQIJCEQzGCw==