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
- 27b2002a33df4fcacff6d377fd6711134a8b1558fd88d5096834c636c76a2f29
- request
- 403793ed97291ba40cb9de5fd62453f4d061b9a7ac54d2ce1ac3521bb2672d4d
- transaction
- 7bb73e0f632e2ebe5f275bb68dd0988615b6eadbe56d437cbfdd4d7afc1b83f3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67504
the chainentry 67504
- sealed to the entry before
- 2cf05a035f725b28bd48cf7f0f4984b5fda079401a1850ea572cfc03ecef69ee
- this leaf
- a036852e5d27c2c33d1e71c125fb9ebc3592fa05ef112304e54386abefad9023
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dofo1l0ajE1qok0MiTtMP0gdDDp020/liOzlDk0agQJ9KVLPcHMaGoVokiMDw5t9vO4erbs2UZUqWQM1QDPwBg==