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
- 6e6f61b7dcbafe95e0295f42805f628fed4a3cab75bae890896620ded4212117
- request
- 4f3332af934d98b1b7dfc482b7c91816f13a68a11358dec75b6e257318efd4b8
- transaction
- 8ea6b6ce0dbfbcadd1eb69142ca308b4c8685645f498ce92284d1dd567feac19computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26212
the chainentry 26212
- sealed to the entry before
- 4a713813de2fc334fad7e35df65a1a7809092cdc1aa95b79d11784650f3cb4e1
- this leaf
- cd5571e913fd15c46b3256850cde20e543e92572a11cb1fe75261403d786cc73
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1Kwnll30aXatpmopcMKZN9kmOq4ryqyAomlA8S+zdJWTxURVsXzTqyhePh7flEKIWonPgrOBygqmczpH9PWfBg==