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
- 085a0023c2ac55a544ce52eb561fd9face6e37db43d7a06351a35a328d5f0df6
- request
- c58063f9f47e87f0241552b386e107292c23eb9407ba10738a31f9c78b6e9b37
- transaction
- af016599a2476f6bb4f53c44c32535e52a5239f4dab971e4deaa4a9e3cfc6776computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63605
the chainentry 63605
- sealed to the entry before
- 2ed086dac2e87ea4e38875520910bad3ef8faf978851fad90a5a9d8cea67a0c9
- this leaf
- 7e27621cad9b0f51d0ebe96dca0f1ecfcefa78b22fd630f3f268ce9eff74832c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2YfT/T5kwuy8pzDcwnvBi/22MeAoJHq9DvVj9efSxLgyHLTm6BRWaEvoRfE4V9Q9XUUuQgf4GNitgq6CE4oTCA==