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
- a893e0ade85ea4675255bb77bb162323d61ceeb81f0d7b749911269ce729adbb
- request
- 518e5b98e220370a4f2f340dfaa60912610228b2dea8638fb58b773f9f4140e6
- transaction
- 7c0caa25106d7497f9dfd66fa36c1440b892c41bc72c7f49e50d9adeed57fb10computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36698
the chainentry 36698
- sealed to the entry before
- c7fa62e8fef54e594fe3ce64003a662abf070a0e81271ca00360e9a6151253a1
- this leaf
- 0525b506acda72292c4a393130cc716d32f64fbf85584af8bdf2eb179e25ba88
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xW4+Pe/kSoYfI4Khw+sJO8dMIEkLAnBETROIEclUPa8ZqSL1v+9W1uunZ8uzFHOJEpKnlurUS1Pjp6rehTxNBg==