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
- f932bf22afe4d71c044ac26995b45465e756924ca2dfe503c43db5ec9ab5093d
- request
- bb135dbc660e69c3d20689cb1cbf97a7242cd0d29f84e761fb6395cf25c3e6b6
- transaction
- 98c251b915136a2faeb6937bc2768b225e0bd69aa8d33ef094ed0d6962178c5bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29788
the chainentry 29788
- sealed to the entry before
- 311b1fa16cbac6bc001975e5e0e69b5ea8362e46d1b13c4fe693dd827e66f4e6
- this leaf
- bdc347fa880b75b42ed26b62fad2461e47d9472f5101ebfae8419479bde18a8f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tWdSofHQVDj/WWvImgVG3jXljgttlt9pnKHh7ROz2POxCJxkTOIGI65R9jF8YlAgpF1uf2holLXmYK/qrmepCQ==