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
- e0e5ad9403568c6be757bea3fea92ff964997d97e271dd8204ea6a12be4ce189
- request
- 27f3a2906600863697ab3da383183bd85b334d467c60457265da1759a41d09d3
- transaction
- b6e9db049e70d8e8acd17124a54be94fef7ea31322bab54ef864317a01d5335bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49789
the chainentry 49789
- sealed to the entry before
- 9bf7e5db33f61302700f91e1337bea136e45df87b5adec5f18843dd49d48fd71
- this leaf
- cc63584563448fce1fa0ac5661f37b79a54f7cafe5b98154f752619c4e419147
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HntSTa0PMrgQh3h0skj8kYuC2G+nvXiIxamk/qaTscoGX0AlXVlewEDqoMI1YD+nmNcagJcoQlUpZQPfeNT5AQ==