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
- e9722fe6905f49822318f39236fb1ddddce4a78e28dd8e054d62ad24c5a6131d
- request
- 3ef1571b00037cbdd99fd8828662182cd252010bf9105a9eb8f0ad5ecefe357c
- transaction
- 6fb6eaba332ba8f86ab5bd4e3326adce8154cc6cfc76ff1e7dd212df5c10388dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67524
the chainentry 67524
- sealed to the entry before
- a634675994cef1f672240950ee03398ce79a42551b1f41ea2ff3e1611c7e6124
- this leaf
- d73256b5c8eb57c11c0322f96eed33b4474c0af9009f370348266108d390e3a1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EGasqSxI2a9lBZzDMcLAlqamMQ5tc4TJzXKJTEA5QlblPYZh2Sptm6lPzuucTnmfb9H0cQf7/Sttuwz0MYv8CA==