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
- 61bd4aecbac34a8f2f2b1916200147f42f109832bfc92e0310ccc04dd1cfccb9
- request
- 4355dd8bb4f9e4263309dfc8436b06d67c42c9a4908a52ca199c6c9e1f1073d7
- transaction
- d1d68dd7e739f1d39f43f3f9a919bc5a3992e16d5b35c90ec2439ff4f47cff32computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31872
the chainentry 31872
- sealed to the entry before
- 11f17e592ac93d8ad4bd3cbdf500b181bcf4eaa54916c7de75eac869c0bd05ba
- this leaf
- 48eb6121cd0d87ef1765ed5013d2c46b5432c399aebc3778bbdd73e9d8f5e134
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O8SRdkroRDG7QvhkOt0o/LMBalsaWi30kkVLDa+lE9Gb+O+hztO8BQtG7jdMytyT3xh94o6LE8V+sHmLWcQVAA==