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
- c5e386f9e4579c6f8943a09889c0a85a83aa363e364c7a44a197284373cf069d
- request
- 9c937b7bb2967176699ba461ca8202cdffdd2cf3f9c4a7d55a3328eb7cc44ce0
- transaction
- 58b09b57bcef7a0354163de0202a1632a093a4a10a97938857cbf7559dc2a975computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69290
the chainentry 69290
- sealed to the entry before
- d3fddac72d6fb919d1fb737610869fb3a535cd57f8d7e0fbe387dbb8788d1822
- this leaf
- 881222ab57ea8bbc3585dd2e252a2957db05d13146359a3e6500c473cbb61018
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TEyEF0tzlD0/WdzUGh44CGMS73jEmRUlR6td9xGQtE3CrS5EupEgm9oBdpN3JH5l5eT786FFO5QNd0qfqaAaBA==