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
- 755115076e988d4375f070c27a39e229de38d1b549c88ddbece7561187f6bb6b
- request
- 18969e42cc67b163cd11a5a42d7ab77d6d6a464d0444169345143a1147121455
- transaction
- e45eee7b539e79cd5a4de61f1bbd9dd8cb16ee973e2685b734a903e430ac5d32computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8419
the chainentry 8419
- sealed to the entry before
- 8974c61160863f91128c95bea9ead920a2839d4f2d8985f10a7ecf84d99ed830
- this leaf
- 282cc53578dcd41329c79bb9f7400b4545cc47ff055db6e98bf0ed69add68cd4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nCxwnrVrMdZL78Lp3RiTz8aouwLE38S+Nzwb3hFzazzjsjnSvndkoUeWRiIaSUEyVwcyBu3JMQVt98bbtfTKDw==