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
- 69139ca4e279fd462a8940f1a104af0e42caf34ac25a9aba5c9598001c6271ee
- request
- 078bdcdafd7375a8ab00b7819bbce85c73f1354f1a86c162f799fd1817dc102e
- transaction
- 6840adf23e51b7b8b806e3233d68be4a2af4e4f022844508de0226afc9c6ba03computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 591
the chainentry 591
- sealed to the entry before
- a44690d5d9c2c604707bfa7f80dee5d9eabb2e8a16d54dd936bb4359d2b74d37
- this leaf
- 3bbe99242ee30d791191b92c148dbc1f978f7a15474f48446add483b98a5acab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BAWyceUDkkTsB+AK/EkRWT3oETfs/ORfYYQXneGQPiQeF+334sukxkbh4AzEqKh6EeN1ihoIZsrCfeK8LWHeAw==