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
- 00357e6c5f8e3f801f4e43591f7685fc1168fa68eaa7ef4eb08965ce787a27f1
- request
- b96b9f7d7c0fda93a28ba3c36938a7da4c53530151ef844b07cd91b54e2d52ed
- transaction
- 01579afbe0c4edcd190de597b67066281afce5dc448e556d1437bf4323f2a7a1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24882
the chainentry 24882
- sealed to the entry before
- b4413c65e166b1b6ef505619710772d80adb2fda06f30f27d9bdd11ee826181f
- this leaf
- e5dd30d55df2af01b8c5fb759283eb79b7747bdf2f2069b1e6048578f79c13fa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CyvcPBz3LyCA3SUF0M61ouwmh7McQrkt+vHVB21+Ep1lF/yhAShsgXsWZQ+WPUQhj9LKZX1MMzqmlQiQxHWgDw==