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
- bcd9fac44210e525ee25037a48d79630e57da98d1e7899376442cb4e7d8c316c
- request
- 92b9c60544970dc1e48940a828fdb43c343e11b7f987847a1751a08944ceb972
- transaction
- 281f836b85268eda7724f99bd5fbb55f3cd81619ea8ab2a5101304a348fb9269computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2205
the chainentry 2205
- sealed to the entry before
- 0132f9f8fcfae5cb520c5ff6a4d889fa595df6df43d511600bfe96f2d5afd825
- this leaf
- 318c3f1774242efe2945bb565bc631567a6307480f63b8cd383170c23fd1e885
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a/8m6FUfCf7ojKlE6yLKPp6zbJ6AfUTsBiXmcwGZZgtXZzSJn/1mfBPvzPYQVk+a8rGwNs4OwBf9uJeYOQyvAA==