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
- a9c383622c700df42b96acbffa1c130e57b73e4afb294782176cd42344793975
- request
- f1e798ce5f55c1059aefc003c0ee8c96a1f88b2518312ce278f5d7e326ec28b1
- transaction
- 081f8dd29c9c5b2c57aaa0a585e0c93f9bce46e530051e13ce7ddc197c0f8438computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58142
the chainentry 58142
- sealed to the entry before
- 243661f17c760a485f43b07ed16aca34304d22dc1f77acdab103db081fa54e78
- this leaf
- f9d1fd89b780c28be314194625b10bbf3c35ac1ed9a5c3169e100a296651f76c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DkP0579hObNP3Vvo5wsQdBAbPrM9PhHyeSJhay4qU3/0+NR7X5jhnh0OC0L8AZpSom6wuHYaK0ygMhT4Ie1JCQ==