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
- 595989ce5ab688aeabdb74d817b2fff23e408fea50a14a76cb675d77697be9a7
- request
- d232e6c8dbf9bb93c5be9ba4e1e9915869c5565f35842039a2a5c5fd24a466ce
- transaction
- 8a9472211d073d39e5d2bffe848ffd3c9413bf3625349c26a6bd3b458d272297computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9392
the chainentry 9392
- sealed to the entry before
- 2f8a9305166bfa3649be22d8ee020d5022d50ad360559b9a1d24a193f2ada396
- this leaf
- 310fc74e4076dc8ff9c9f41dcd1c763bcbe2eda50ec8e4b43654f123f586f397
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lMyLnlQko1U+nwzgCXnBooxbM23TcemMo2V04ViAKafUzUpOwx9KkEqh/ucghd7ebQJP1FAZ71JZ4FrsNI9aDw==