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
- ab489c4825da7a6d8b646b0f7cc01365716904ae6c61406189e4297bacd05606
- request
- bda0f7c2acf5dede1cfa4001bd55165c4a5d8fbc12746d7a81bfc793e6385ce0
- transaction
- bb418e4e9d8aacf6a8261eb77422669cb53515a20d76ebc19cdd02efdd9b01c3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75015
the chainentry 75015
- sealed to the entry before
- 3af8c7817025c686af3bd7d5c31573c5cdedc056ca03b7687e79288f1d12028f
- this leaf
- 72c15299da7ec20dcc856950f5c7e6e3bf8cb1d9b0d8957a089e28cfd1e899d6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fbrRbmv1BMAelBhBCLENNLGKFH3kYjkBA09kyWGwN9XX15TJNG80J0nYHUS4QEQjXIEkmzlmeDsT1inl9HqkCA==