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
- b9813edcac9682eb5d7e4bfa7bbb49abbdc4446dd5ac1267b144673545527d68
- request
- ed46570fa5efc9f8ea166f7117079071c40980fcc939c045866d562f184c4afb
- transaction
- 1673eb629b443fd0739747e89df1f7df0365534425088f90232a0fae391af082computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19425
the chainentry 19425
- sealed to the entry before
- 7378f9814aad7f68d71bb045b817092618848a64e6fa93dc097683b352fa952c
- this leaf
- 6304b749d38d9518f71da7536118af91923a930472823c104beb4a065bbf8850
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +OiVwLNwgYOInmn0DrgX7cBamAt3KedafSw9kKRwrdvI/EfpkYnQHUPwIe31PZWvEODJx2kMQLzD11bcbRnBBg==