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
- e3da71cba583667eff5aa40af8418d292af9a798906c491c12109f8738232011
- request
- 500456adfb6d7b4ba8eb4a70352584d7b5daec16e678cb3b741e91805248de56
- transaction
- 717cecb4c2ec21d2a524a7d4a81b4d081c63fb3ab59e3de5f1cadf0c73729690computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52028
the chainentry 52028
- sealed to the entry before
- 033f7283b80d8fba082cff1009c1d9ef497bd2307e8c842faaa99a03991a6871
- this leaf
- ea01fef92c01e15633d01f1139d066d4f3994577abd85378f71863d3947a72f0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- x7m3VCU8ylb6Tk7IZ52M7gSzT+qzwRUWQE+ZE2RzLDSy8kh3tok7RIlkDk5pRNmJ66uDrq5l63vl4jF5GoxABQ==