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
- 3fba3693128b9e561710d5176b88fc05ab22468cc54d30af6d31582f158a269d
- request
- fd0f5b2aefb15cf3aa75d7535b003e640c616aa24dd9d371ec5e1915a6372072
- transaction
- d5e16ffdd79ea3fdd6450d893193a4bf092170ae3617ee967587719928348c4acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36737
the chainentry 36737
- sealed to the entry before
- 257abba14cc6a2c454e87bfb3d77c415fb8f96aaa5d5b345013a0f9819390e3f
- this leaf
- 1af32b51dc0a211e2353fcd41717d14c2bc8a0c158125f7a99bbeb4cccfab389
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sQ1ZzosC+T3ZamsNAbuPS6NZBGeFXgSYG03XXKTY0Q3ggrGnJAjyjzo1f1tQJkIg0dgho7bYI+mLZK7fh9mYAA==