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
- 0a80d80e36719309124e5af068c4570fbe7b01823d70bde2aa52a9070acf83f5
- request
- 8a9cfe92bdc11627eaf0c3601986f64c56b93fde67bbb9cf8a143bea57cad2a6
- transaction
- 77af1b538b744e0fa42f4afbe8144d49a84f9873ce5d02cdcf611e2f910b0cbfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2465
the chainentry 2465
- sealed to the entry before
- 83637093d956590e609cb5102e0aa699e7e5dfe2aae9d37ac942934a20dca3c4
- this leaf
- 75fc812cfd5971ba91e740ffdb81f6dff204ecd5ac7a8da032c62eaea9b1cce1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kma1opkc6UJyje/skcdjdtkrB4lxO7sf9vaj5CsdYfHKZWXP7nOl9G+jSAHIBuj2FT6XN3ZTmHYyCKJTvHF5Dg==