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
- dd41117f721f9e6eda8fe2c58f869118f7a1b7140a9ee443d8c22b7b19cb4d2f
- request
- baa52bf0237c5158aeeefbcd79f1aff279d0979d315416096ec659587a18ec3a
- transaction
- 93cf64c392594048abf6c315e72900f03676c7030065e4c7645fab8875359d3ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54578
the chainentry 54578
- sealed to the entry before
- 91362c8fd9c2e96594677b9e5c8274bd9f09ba6da17a2cf64e9608ba20539117
- this leaf
- b5a6f95779fd2ab6c3adc7be0d469e7e7012160417035557b95cc5622da11e41
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +4BCVFRO2rhlgVoBb85WcvxDid2RkhGC0JfBfhOWHgN0iA1/jzVtekKqqjZtEcuyr6Iz7gqWF6JacWkHFqtdCQ==