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
- 4cd4bc7e6844fe1572cddc0cc59071c1ae97240685b3ad190ebcc01b3044bfb2
- request
- 520f998a51f8543ee0f58364a5af89db49a4d0f300c795971930b62bd56008c5
- transaction
- 96269433d29d7875991ff715cd0a96c5ed7756f6208abda018c4ad8a6de78cd8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55131
the chainentry 55131
- sealed to the entry before
- c6e5bb2e0df7111bb6a19a87b0ef519010649be5f8e38abb397e82efe9899674
- this leaf
- 28b632239f65890e4697bb3f01b2f466ab29dd3ef0cdcc0cc7cf20bb3a9ccc81
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- M6bDYvbfwBJ7cF1gB1jfFv9VyBPQq1dexKftsFJr5jtoM1qiGWtY+8/vnTczSTkHZFH4y2h5NIZ/o/9DIcLFCQ==