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
- 6f8c6921a5a03c33cf7414878b9e47bed5c37bc34a336ac8c3f3af2ffa830f16
- request
- e59b34925a3977c399adcfbb60c6400fc72b6f1580145b9095b4bc67ee074625
- transaction
- 959908e20041c60adae7b12b054036978fa370d003aee3b14d62f5bcef6808c7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71276
the chainentry 71276
- sealed to the entry before
- c8dbcf248c77e63a53b9ba83bcbc359b168f69e5e2e25df3ce3f2c32e7981ad1
- this leaf
- d0e2c1327ae9018fd72c2f105bfd4642f9a490754ce92ef05d4f869b75ccc46b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MHFUF6Uzckgj3yDjyKRrhvHPQ5u5LlitaPrLxqgCedWyg6mRYm555ZrqAU9iQJIBJS9Qt+nxIZiUzURfF9RTAg==