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
- edb3f42eb3dc00128a587c9480c2cba53a310194efd7c60602e0962a57ccd89e
- request
- 4294dbd5d2732aca03f3793b2f5fee32dde2274c7e3783a32cbb8d8913113e99
- transaction
- 1ddb2a81a0c93546bc81a320a668b59a78234271b493a3b5c11e34954650c595computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33867
the chainentry 33867
- sealed to the entry before
- 6deb8b60c22a9b7c01ec77ae5f67994cb4f972cb08366db68b2bd7acbfefb92a
- this leaf
- 9f619f049b6d5b03f8ea16ad621777e924a9dcf1eb28a9b12298f94e8595582d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fA4TmeQtDty9Upxt1ITgKxz24/xw/IIemr6x14VcEzdunP5txVskvDfqRKk0gX5iWIQpcVDIU6fQrhmzGK66CQ==