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
- 113229b8282ffcd6bf731f779b88a7436b862a6445e134d1489da579f1179fb0
- request
- c2910b48f823368160d86af2c5a1a3a4172ecea4259c2ba9dd3696021956c22b
- transaction
- 17b2422bbf1de953ade4283ee05f4c8418496ff9aa563a3814b1375ec3cdb1afcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62859
the chainentry 62859
- sealed to the entry before
- 59ac541178a71b6ced9421b7fb7853f41f11112c85a4aa80b519cf8e1ea7d11e
- this leaf
- 03a44f52aa764a60146339b49b13a44237074097f6ce555d078fdbd6f56eb446
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3vNfCvzYXciZeWyjq01Iod2sKsubny1UpaMjQTOrf1d6NRDOH8VJrMbxcStXHBIu8UU/aCBDEgAmKYfWrLMEAQ==