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
- f58bb9eabc692e3a8dfd188e77b5f5aa4d8fabe089d1bedd6f98532ded6b73ab
- request
- f54c9e35d1641001496d0d0a29e7f3689f51c5037c40cd2d58934899f68a09b4
- transaction
- d7727216386357af2b19b0c659c84c816efbaeb41358998007fe59529fe9002ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40328
the chainentry 40328
- sealed to the entry before
- f181018d7424a9ddad63ef2c2fe95ce45b76921386b1e6d989d21459a3cf525a
- this leaf
- f46dbe77eef1962d38dcf5022c19bb8403f4361e5118aa126985bb3ec63f9903
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- W7x6T6KlXKlHImCEyz1XAD9neyMI5biTiFtsAJcMxq3c5+dD8GivTw8IKuYkpBTz02BAszpExkT9pNEiMfGIDw==