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
- 78060e657f2270488c6e10b466631c803c8c787feaaaaf4ebfa3abcecc5be918
- request
- 71ea52496e0bf28b95403f2c62768b89edc7b2841f06d4d374a787a69a58a156
- transaction
- a5c6345b797da62efe1d64c2722472833aa1bb59e179e68a0bb43a915c82fc71computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27236
the chainentry 27236
- sealed to the entry before
- 11ab1e96d9812ac97fec687de6615060eef32e3dc862433b77c2ee0625f3de0f
- this leaf
- d99934a38f09e168fa11eb96e9c0771adc9c6370279906e68ace7ca6b450faea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- duG1SdqG6y23p60r1rk2egpZohMmtFlBP9Vs5dAUSzN4LgTTwg67VHu9tAYqe1D/6F+SIfgE83XOoyxrrhqsAQ==