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
- e17a0894cf886efe05d722ad9b5f444c84cee4e7a8f097765697f436a6777482
- request
- a21b5dfbbb4b9b59b1c5f0a2cdb8ea0bb614d6f0e52c3d2eb92802c11d023c5f
- transaction
- 6e06a1a4d54d7a70696329191ad5aa253f55ee5279345512ba4eb01944d0ccfecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46046
the chainentry 46046
- sealed to the entry before
- d867bd38ab22c508f792abf79065cac44656734a7a972c107d4e6fd3a84863df
- this leaf
- 3654ca45b8109972e04cb2ef8a7e8ecb65164b0092074d8de8689003df382d7b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jM3la+z9r0j6NRSK5fAYuadVM3ku5k8jQ11w3T15IIdb9JaBRk5zBLPYEB5DCYbFl7sO5rcW3H31SNG3MKWgBA==