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
- 2e85704da67d1316df25d137592dca34c824c14cb9261139d3dc71d3747bd59a
- request
- 04d5d50195be0ce75f8312a2e32bfcac8d0378d0e56f7e69ca9a642e9706830e
- transaction
- 880c13e5a692b25a77d57d633eba8bcc2c2e9cd64a5b41b70b1f769c9cbe2c2acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29880
the chainentry 29880
- sealed to the entry before
- 41a709e1b80db156c6426645e64b03d98dfb8985d2cc682551b8d2765617c935
- this leaf
- e2d0942e5bf52ec08c8585be685b79e1f8dcd5e49c2f41a4081ed1b15c00b174
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F5OdrvF8dUsQwFs7tDwVrIZv2FjT42e1tkj8FS44E14WHhpwP4R/suyZMpdjeZCWxzb72Fk2HvCjYLPvDoZHAA==