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
- f4d95db0821e5cceb988ae622da65ad9252f68ec777e9fa9e5d4b657fc5e3f47
- request
- 69ef9607e6078ced492566f6c719ce7f5f05f15e3d31a2c0e94b1a272b964a52
- transaction
- 306fe7c1a2fdbd0d33d3675971376e39bd8973a63e247043569d4ebf085ecb28computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20366
the chainentry 20366
- sealed to the entry before
- 6be0e463bdc70dc32687750643eba0e20f3bbd067bddcd6a836854bf9a2d4fa9
- this leaf
- fbe026faa9f6c9f55f372ffc42cdf53124d166833067563fe407f69f78849c17
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZWXsReknOyjqTJdydUXdZ7MFXNswn13S6B7xvt0EtfTBeGd/kye5SDrM7pVMaeNnKXKNjHPyCy4PqsjVL8qlCA==