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
- c9beb65996d13cadb213730fc2502e807971e318a3ed069034b999f30a69c372
- request
- b365f81d5c277ae0e504464de067fe1b27240f6c90febfd718e0630e35df1044
- transaction
- cbd42abdcbc70c294307230e8f8fad658d3f767d2e95fd3dae3f519a4005c47fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 801
the chainentry 801
- sealed to the entry before
- 8d3dce369f0a9952e0b298478ced52cb74961ad02d78673323bba830dda18c57
- this leaf
- dcbb04b4ade4888cc0d700cb2045c78dc51f35540dfea1170dd52e1ff72c8684
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zq3R48dSfOiJsBdyRHJWSDX+3U6Q6rA7dvp4Os9lhyjkoAUjdq50DGopACaQKQedLH2i9uQyAhvcC34WKRxECQ==