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
- 2891ba4611ef5b0a6b58f53e584b6baf156dac7a67972ed143810e104f9b3c07
- request
- 24fdd2fda623e47ad5e0ce662bc3b39f99ee872b04c7585836ba994a607bf1d3
- transaction
- a7b032fe4cc8dc18429466340acd0d0f3940da42249b86472ee199f9c3e922afcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42413
the chainentry 42413
- sealed to the entry before
- 02d0f7d74bb59e67ec3f3e14182683e4f807a6613f99046953589db1402e9b25
- this leaf
- 1c39b00686a8ca88962bc56911b40445f7cddf718f559740c0e5a670c6ccd391
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CZ1MTABukXh6rCI0KWBt5YpNwR17LI0bRx5k+9OvvBA6zuaA3LR31rqZmp5fET1F83fCmUr8P6zx91n0abjLDg==