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
- 5fcd48afc542e68069a13dda057104e62e62756f0d2b237189ef2182f70352e9
- request
- aaacb07aa47b0cc4bd8cb3e60b36e7c3ded943cf509c2f63929c8216301f40ba
- transaction
- 98ebdb84878cdf85d95aad79fe600e20c0e37b7100214f3f63a1acf4e6b3e31fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63198
the chainentry 63198
- sealed to the entry before
- a21096970ca069a2579fa73edbf28d0cc1ce6258906a44e690ace78afed5724b
- this leaf
- 968e4d101a63d4280a0208f0f726c718c0edc7ae3dde996f66e80a186cc890b7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O6AlC8bU5Lk5CqZohgDfdT6E/gNVBSl2UlWtBku8g7RtH8wWfaixWovkLG/WTJyDaw1Dc5ch9QS6e9n+H5ILCA==