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
- a37d27d127073ddb815d61b04dfe9aa14517c1c94d1cf57bb93383a8f811ac74
- request
- dbf259ffdec9715a9790f682135f50b511795e1dacb7f0a528ddccd14c58fe02
- transaction
- 3e3c293c8b3aed9621ccfc1dec0f74f94b58282467ac41650c42aebb82008efdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19184
the chainentry 19184
- sealed to the entry before
- 780936d639a5aee19d829cee144c3e9b8d098d2d4c78c3eb2e887308937562c0
- this leaf
- ede5b0cc49b9986cd08e5e0594e5565436112e4dba4cac514b46422e2cca6640
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2hRKF5waYGdAkk6CZlOcp1e8AUJGQCQEC1jvMLlTnRnkkJoa7t7g6BoCLMflQ926IMV9I8vuRzlGeogeRY/WCw==