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
- ab86f8349daef06d729841ada045dbab96f5140a7d4b227320b6843039f01cfd
- request
- 3d6f923073a2879631fc0bc2d53dbeaa7b797a4a60c87dff3ea5c0fe5e1aec40
- transaction
- 8cc36e594638071fcfda3a00902c8023bc483b076b09391242f3f5d67382be71computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1725
the chainentry 1725
- sealed to the entry before
- daff29fa7e8295b07282db771bd277c142b2a45e15a0cc87e993cadd67c82e35
- this leaf
- 18486aa28f502789ea4573ff2cd66a43c2b049f6ca10434a0ad67ac428e78c6d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CkHqt96C+A0zHxbbl08kIjrNMg8feFM5mlfnKOadSrONQfdK8hrQkFzuhbKYnDlrcuHPSjTXViT2G2YYveZ7DQ==