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
- a54ff44733eafc2d298309b11b70620f9f7e7ef91fba7b61ecefe72ec535427e
- request
- 4054fc03b1cb1505746e0d5cac2d43874317667b9e90edef1a2ce5b227a85ab1
- transaction
- 740ce75aa079fb49c96c7c4549ddab913813b880073ce9246d4609d5bf8f1f83computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35161
the chainentry 35161
- sealed to the entry before
- eb9bd6f8c76006df7b15e0dc2f27a20c3da3fe58cdf9a056e523c48c1c3232dd
- this leaf
- 712e91a1252f8cdfa732b86556aa691cafecdf8f77625ede066bfd8a6ba2371a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FneYDpkxz8/RgNFh6A5uxD8AT/ky0WZrk0ltyMMcbQDRHpifTZvEktDhoiI0W6QFynFTB7B0R1AF00Su+QI9AQ==