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
- ef165ad988cf130c0bc69d119361f41d632c17fc04c52c3056fc3d790370da79
- request
- b3245defb079bfc85a55d940e540f355990d829efca1e4c5e33d502be150c8dd
- transaction
- 6be1f8c6c829993e60b9b4ab471bf1f5d5ca4fe58cc19ae603abf38ba61c1470computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9551
the chainentry 9551
- sealed to the entry before
- 976a9fdaf8bf4011e4445507650a11c3a0cc6c1da846d0add6dece280d238da8
- this leaf
- 8cce87d9712f65e402112596830b756d65f65be7e8545833e69c82341d2c1e1d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3YPA5wFg57Fywmj9mzxY5ku8vc2at+t3j51ey188Ro1NJzl5qeHCy0V0V57VEuaDgwzwPvOjQWGnVcmtlYGBCA==