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
- ea7c5a6239ce7ebc426a545ef36b1fb78a87165a382f109637cec6538ac7ee0f
- request
- 7106ac93bc24991c654372090bed297a821f9f8733168a7f9c15235f00461592
- transaction
- 7c624e11d5de9ce397c4e858f3cce79a119b6f994e71b8ae624443e49c13389acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46833
the chainentry 46833
- sealed to the entry before
- 74a7b3930260c5ee7a3774df865de3b06636a87d14caf75fef8a53b4f2b6a099
- this leaf
- 6b4d3a196a7b8307a9f34f530c636e7c3d03d075944d0d635e5bbf94cce4854c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ukQmp7krLQKtK//LoPofMW7ae0+5WefwiHqjWYk8L2icuqJBIq/csXxy9u7EvuoievpJb3CG+Z6W169cizVzAA==