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
- 36635bb0f92efa95ec082d263a7a7cdeed47dc7b7d44cffc251c7d5fc0e577de
- request
- 75cc4bf4eed4b4e6be3dd554258d38e872d1b361ad5298a8372fbea63cfa779b
- transaction
- 40a50f6fb2414ca66831e7a0c6f63c3512d36f9eb649151ed2c7e0c82808d1c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61158
the chainentry 61158
- sealed to the entry before
- 680c0f8a90d1b6aa586ac8f174ece63621fce506f4747651b99498e6310c778d
- this leaf
- 119a78d5f51bdacc4ecda0c66b2c70fb3f329eccbcd80d35e7a1b49f2cc66dfc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eE2Wkockt/2VwbphjKqSN1F1ffKYo84IyBD1JiBg8aPT9antQOFxBMzNHrak802OKtnRU6u86LEn6d5FIDi5BA==