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
- 44ae50fadf35d11dc14f1cc0ed48fa7a3dade5e80b08f4098b629fde9a894aea
- request
- 5e9cffefbc30c681dce65ca4fb056b3582ffdcb4e1ab995fbebabbc420b831b2
- transaction
- 09049f85126f933ec784e8e240264072bc2732bd4cff4808bfd06dbb81b61f86computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57045
the chainentry 57045
- sealed to the entry before
- 940191f88aa4c3a429fc446c2426325f6d006edebc3eb1f21b2239b349f1f549
- this leaf
- 210f5d45f0054e0a05b54b309382aef3dbe30fbfcd72036e863c25cd723fba4f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- I4uHi5ab4QqHmhCndivRN8oNRYe7BdzIGCHYtaCMtBydC5LkkVYgKIcMXjk8FFSaQyH5xlQmFXVJrADXoI5pBw==