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
- ca110a414e2d2efde73193d0613aab589717e41dfe11d620d8411cc1d4da91f6
- request
- ae6f0c0c49023425f43407d00d468c3237527de62e479797d8b418a871d0bc1a
- transaction
- 69b5fbc74943f690ecad3c88999af378e34da12ed53daa483d985496a5239591computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1315
the chainentry 1315
- sealed to the entry before
- 51fc8a20248076c96f525d0e0ab89572657b2572862610bf09efc33289b2d813
- this leaf
- 58d6a416e0fe33cd7b0a8321c225796df71099b2f558d95ecae2a535ff4a4416
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AVNNK8zvNEvzr5rTr7R3nHrC+jIY1g7DU4RB6GkuSNjdT6kuushU21dCUxA8RBS4X2M+Ui2SkLRNWqkI/5OgAQ==