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
- 44b313a686a3b516c9fee0334f38ab39c1451f6a47a69671692f6d3c2de0d4c3
- request
- 445678674706f4ebf2a86b945a457984e98645173dc21ba94a667dd894c49436
- transaction
- 070357ef5cf0a550423e54e61aa6c288b2489a5cdf7f6c4fdf5357c02fe57cdccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76069
the chainentry 76069
- sealed to the entry before
- fa9bd5e3bc37c00a68cbb40ea63fda7ec10ed75fb851a6f0ec45e44f0303c178
- this leaf
- 1bf682bc1ceaf6b212c4b4e8ff12dfaccd7a1ffa2386a090624aac940bc32e2f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JJQ8ki9nu0ae4PthiS1fV6sIWQ5hF4G+HJkiLgBwJeJPxkg9b6eymobSjjQd1/jNhCvWM7yK6J62tqWY40AxAg==