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
- f9f335e4d355ce6644a66f5002cfda356db19a63dec6bc47c271906dda76247d
- request
- f0fa3498f79298f86bf0867be6d689d4316291d6852f03060d3813bc6e55a3b0
- transaction
- 21ad9acb75ba364b0a587caa2b64512b5ac0988136a5153f8bf3147a7f723079computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50931
the chainentry 50931
- sealed to the entry before
- d0dc1a8cd148d6c96892ad467f3471e1f93651d130dfc0b760fc9607d5cc56a7
- this leaf
- 3cc2ccd1e64d4134aa694ec2a5928adc75911d1812bcdd90eb5e7b42e41ee82f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- boiXAqebj3AfiuC9ulfkqXVeUotvquNNJS4UuN413m0CDGPV4wxrwKrOFOb5RoXbCyzu90H4uollSYi5gizoBw==