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
- c5f0c5d488a6fc37a6a92acc8a46bcd782b447311e7d23c3b5eff9365ec94e0c
- request
- 869397fbf41763ab0abbff446572e3bc937753ba4f278a41f10943e15d777637
- transaction
- 82f270c55c00a39b52627fd817ca920aa59c9d881cba7a3cf927e1da5fd7f9a4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62942
the chainentry 62942
- sealed to the entry before
- 6f7da2eaffe48a4cfba4fa1902ef70f46d2b2573d22aa0e5dbfeebca7733ab72
- this leaf
- 2a527650fa1dedc54b9d98f6a989f232e4b5db28b6f774ca7a45a709cd4f9e8d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mid5NHU4UGoc3K4ozT4DurFOMbq837vJaI66EZwuZHUsEOqkJ23+Tt0NXUKw9zCFuvOEP+AvBML+WL1ripR5Dg==