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
- 03bc87fd7c2fce0c000597a8a7be4a38b4df84dc2808fd0050d97d2e71741cac
- request
- 18409e969f6ddf05edb703145de5c7714d639e7f7f84f105e2285a7d20c8575b
- transaction
- 3e4ae46e3bd47c2755ef6f8bcf952e1a72e598597fa1174b851439fc41d71680computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45245
the chainentry 45245
- sealed to the entry before
- 62a515afd6bbd2b615adac251ed9a70177df8305482124ca6d6ab5080e113098
- this leaf
- 3cc05502df527d929823f64a1da24a987d194e726e4b9428aeafc0140072cd1d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q0DqCeXDIKxmKlYTM0U2qyJULb5NiyvveEeymNW+eEEJfb0hi5dGwfow4A6teuXQp8/iTtwvEuGN1vcGbwRjAg==