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
- 00dec2638a0e3b325c960e91827ab3cd8e52f16354d5fd843ff7202a310c031b
- request
- b24060af76b7a3e51c38dc2e7123747d7f0729dcd829b56f9773ed72279fd631
- transaction
- 5b841c6f5b8275574a770b69458e914fe872345b22e23509100008493f8d6acecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10647
the chainentry 10647
- sealed to the entry before
- 256c397af98f66bcbac4d2a28309c45cdbca89e1b1af72f8750d53281eeaf910
- this leaf
- f4772177c58ce0d78fd342209f79c38926653331939b69b13f1f81481196c898
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uNhKK0+2kNKVEanmm9F3duVm9vQr5hZ+CLDlizCSxywlG29aR1cfpzT0ptnbdiUtEff5hnyFrdoboBrd6KRgBw==