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
- 777a08a8bbed6dcd456dad4055b855051ded0d2de38775facc6ac48b9a14f3e2
- request
- b4872a8197468ac9b5131c0c0f9a1bddaddab1cfea1adfde468232fb5185b93d
- transaction
- 580389f8c038dbc0052820cbaa7a018c208231b99bd382690c8f8e6223a32fdecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10412
the chainentry 10412
- sealed to the entry before
- 81766cdb719793eef29f4f46231274ded3497d7750ff3222604cbe38ba19cf79
- this leaf
- f8afe0eb6223b525183eadb69f7795dcbd7e57ff0d8c9cffe214bb7d5f0f8180
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- A/O/tSDSlp0KV7sYnuwM5BIUlC4xxlTouh9fpB5v6SKswIYyq4weNqMkEmrkQ3CjJPE4pLSpUcXGItDIhMnHBw==