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
- fd818eea9b4694bcf95c22754d4eaa1f1ca374a132083311bf1ea7819f62d643
- request
- 00612662b1b6fcb26c5d63702771bcec884ac9d5173073d4363bc136b4293478
- transaction
- c9e596215eef0e40c25385b72b02fed84ee15fc9890080965061e39a97fc72a4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49770
the chainentry 49770
- sealed to the entry before
- fb88150c7e4f177a18b526ad3fd3547b23342b06ec2c520f44453bc60e7d28f8
- this leaf
- 51f4920e62e8212598d81b757c147be0bcca24c77fc9058d4bf29268e1519e3c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1Go6IZP8S/zbNZMSs0QoLNP6mKVg2hOq/8GUcFGBN8DcHEcpcb8MNUJGyIMmYPTMSpLiq/AOSZc2SIq0W7ixAA==