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
- b3d34f983606f670d9816c8a8cb3c3cfc85be8b27bb4f3a5183fd7abc0670fcf
- request
- d8056be3f92d9c78808ceebe645aa6df028e55c4c351485f4b09cc8267922bbd
- transaction
- 210659c6c413e5a7cd068bf0e39dc28381aca0fdab7b4508ec63594a9485b422computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74020
the chainentry 74020
- sealed to the entry before
- 9f190bb3a125ff4be865b48a052552ba72c8cb706828b3e8c77373788b844d50
- this leaf
- ac43b46eecbf99f802024f4263ff15eac3534327ac6520ab16442f9a67904225
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8MR9j7CJEwirhgc6d4Uf1hgi814zegi5mIpcwKleruECNF8O0AU6lrOp9QB54krYbNg4Mo+Fl2OlLfJ9V2NEBg==