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
- 171b995b262412e7d642cab99db09c841de25606d7a9af9379b3045c9fc1c88b
- request
- 041351f1ffd529745b520b33673844e1d9e149ee548458a6cc44ec12a53f38f8
- transaction
- 3af898c653d205a5e604a88435b45427658080e84c22ed4811b64eab687eb7f2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63400
the chainentry 63400
- sealed to the entry before
- cabf2e116f019e7ac040d9a537f1fc311568731a158de4b8dbc00b84ea0f88bb
- this leaf
- 5ddd2ac45a18e15e4e064c9e1814628ee41d625e4a801ed05031ea49e80e046c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lg6/dTjVsNJJL5q1+Ygk4JYqKpg1q0Gm/hvw148QzD9WZUkAFp3xmxWKxCuntgsNwvoFJKJAyutjSv64/NZmCg==