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
- e836896ccbf3b53b63e89edb6c934b076b6a080ed8c305156d311c2650d3c692
- request
- 9fdf3f6492e1aba8677f333fcefa30bc80300a70521089616822948f70ca7714
- transaction
- 4234eb033a95e9d2bf1f52d6cd63f37717fb243b8f5f4e05b7efe55aaf890e06computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51183
the chainentry 51183
- sealed to the entry before
- d89f2ed6681c435af606e29846f6766045c0d2c1652fb256fdec09f3e30677df
- this leaf
- e19657f11631cae55416fd69326952875155cbc5832b70d504430ada6ace49c3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IatPNmKVBELErZbHLKogXKCJb3s94NZMCxZAHu7X454jslrT9m9Deshu2nwp4GNhNDooL2KZkw8ZlRV8cD4fDQ==