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
- bb3d724bf30289622115977c67f72938b0fd10f6900376591c83df8766c2fdac
- request
- 892f31d80b2340483b2cc92f9ca1687c226424bc8810dffe98fe29fcd81d97b9
- transaction
- b876ba6711cb00b15a90666d8dcc3a42874ea2fc3ab4dac0a6911f2bc2ef5939computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7154
the chainentry 7154
- sealed to the entry before
- 2632075759ccbeef36d125f33a39bc56535060e227cf78277cc32b9fb6a0967c
- this leaf
- 2971c0c58c3a956534fd17e8321190d99479553f19d5676fbe21956d01b0ce40
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sCiyVdOuzjYYCiIbelkjCfmxhJJzanV+AD+z1NxmLURe3ln5E7JGMuDXh5L5ndxSe8iH5B04ZWE5GonOdOPODQ==