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
- e8824ba06377a23c56d4930f142c0f1fbb8cf1b5f956462bc420afa75ac2eb06
- request
- f3ef84e3c4b1c6e856845706429fc41ba89c1f52f38730b98707774d07e6bbd7
- transaction
- 7f38155bc388e356d84d2c8e7531a82f70c0a0a37fa51ad7267598ee6b01c0b7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32163
the chainentry 32163
- sealed to the entry before
- 0375e3299fb9eca6493f221f91517d780505cacb2c4e1119f155d61fc0ad9263
- this leaf
- 2ab3e03fd61738878284b1008f97e9bbe5485b2fef62bb6c967dc55158daf08d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FUNpnY4NoMKOIg25/fhn2Wf0CqX8JOE0mTtfJqqNIhS57JJoBsQE6xpedaY3cW8ZpIqjniNNC0x8DrIjn7NgAw==