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
- e4fe6844dbdcbc078f25a2b27332a68f448b20d995a8ce399441086d3803327e
- request
- e36860f9b69b208c38a8b9afab694e7c6a4f40907aca07e2194f298c624a917c
- transaction
- 785bdaf1869e9dbccf661544dcd8b1488c06482a1031592333e6de196d2e5330computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63468
the chainentry 63468
- sealed to the entry before
- 917341e0b3e3a3556de7180de86a0fdd99e5be8dd45a210b1278849ecfd730a6
- this leaf
- a0e08bcbdccf131e5823a5cd374c9c8d5f44b94ba54b5b7430a83b6b47684840
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uhGicn/ChZfebXQ7urimPnORKSIQ/eQGPBgZPepCTQeuCg5mISk96Y1i9J8cfLGJ3443BAJsOo5Pmvby5iThBA==