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
- e8e1b9043714485e82996059bf86cfde5184ef14404d3c32698811cc31cd2e6a
- request
- 6b2093444f6cd2e42a3e34e44bcd51b83b9845f55b206dfbff24360badf9bb2e
- transaction
- 32ad7de9d26867cdfa0c7e602b1ca6232979528404b603f38cd54ae5e783681fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33129
the chainentry 33129
- sealed to the entry before
- 91bacddafa6f5dbc69fda4f2ae71a2039387655a78ffbe1bdc6de36912c99101
- this leaf
- bbec69905933a2293c7f49dd1d048edafd778bf90a228394beda4bbeb83e5de9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zuUkAhfFdx47uQc+5MAGYF9QPfJo1IrYMUqydQ+JuWQo1jXx7IMYJq/1rkZI1JIg/ECpGNUcthQWFvGHy/g/Cg==