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
- 716a90b8ec2fffd9e47bf55b75e805fdb37d10c59f5f58e61e263954bad30ddf
- request
- 0b0a4826e243d4f0922abb0c483ffebb1ac7b8556c452cd2e6583c39152d3798
- transaction
- 9da8e68594dde6bbd62e86be14754d44d615d6c2389b908bc014e78184fb6f21computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47521
the chainentry 47521
- sealed to the entry before
- 83ee5d3aa6bb2df4efe64b6b40024ce2d8f57634f9d5d4e331e7ed9a2c7987c2
- this leaf
- b7ecd22a2c1e082cff67199b4e8823f1758e820b9b7fbafe56e6bd1c7d10af53
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dIhSWaW4Yvl2WffE55n5+Udu6OD2uqcvQJmnX+BQVyWWBpjH0YhjxPJAlhVd64DSjosWbSLSphnIsqA5Zx6GCw==