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
- 49bc140f6d69d82771d780e976346aa7336018a44fc4f7aa512eb8185d51ab78
- request
- 69cbb9c317fad5047d892c1a0fd4f140ea85372b582571138c3dff7916e437bb
- transaction
- 60548b034aaaf953d1f4f18e36c6d25943ee99c71d70b53830ff18f34018d52dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16302
the chainentry 16302
- sealed to the entry before
- da776d33a3919e1b57bba2d1bf104046f5f269c097a70a7fb7c8baa66c2e18df
- this leaf
- 4f5cd2f43f296da8cc915f4fdb0469cc931888a3f0197902f7bcde8d2cabdfbf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XvEP6QS067k0XYCX7mk7JmWRqO5sRH9h1uKaKylIS7YudSpdGGokmqA55ljnQPycBMf0GPzec6mP+Xg0KvuoAQ==