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
- b7504a14e0acb5deb3167185b3d9e2f2905eb0d387f37f9847a518c8c095239c
- request
- dc4ca27f87aadc41dad2a7c211ac95d43762320a7433313f388037a5bae3527b
- transaction
- df39f33b72227ec679c4e7e287df26748b60af4a156195cdeb38a983e99ffc2ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55257
the chainentry 55257
- sealed to the entry before
- bb826a5f095390c0ae015c0eab1b167c8f0698ac55665a17bcc030cfb717eee9
- this leaf
- 6e68d888b9cd16912c6f02a574e541158c63ee7cef87ae1531a8f485d1662a86
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ELnYGJjzC9vG3WBB2aWodyg1M82Mq71UQXHdPi25f/rcxF50rbROKYMWXPfCnZHKKYnH4FEASrudvjWd7kgqDg==