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
- a667a56f0427b417e873c1783c8a7be916f0a604db34f6ce8ae21b697bf483ca
- request
- 9f39a4f238399a80433e77958b0e8f710affaa54d8fbb2f9a3930eecb761f620
- transaction
- 2a7517e4bb7817af04c76825450b1b21ff68d7addbdeda21b70aeef836d24342computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34616
the chainentry 34616
- sealed to the entry before
- b499644cc6d488a4af6d4d01aa0ed784a0b447a16be2f20e2c44c5c5b6d17ba3
- this leaf
- 7e780d68e8e9bf2eab5fab1f474d81f1eca8f82bbf203a3765549c83e1386eac
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8olS9+GbeLPmi2wjzagnnkFlbba+HgksuXANXAP4yZ4WFwn+v+/A5sn1BGtwyAu6F4cNZCLWxprutI5dIVXCCg==