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
- f9c8e660e3e3467ff1bc8c32061da890e726c2d671bd03176b27a4d35578256b
- request
- 5372d236ca5409dcf15c476bcd2b554a0cf602b587fde1c2d0c9a183c20b56ee
- transaction
- 86d86491cedbe1e0a3f25d6fdd4d3829fb0f14391cea8494414f1281c3e8b38fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70835
the chainentry 70835
- sealed to the entry before
- 18e8890c10b50249bd820b0029480b3d2c8916e1d4cc795e781fc724d570e6a5
- this leaf
- 25eb57af19438d0f8c5d396f73f7ab7340f0c62a9816cebacc5a4a4482e71018
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8uDn2mnFHE2nNKIgYMoTImQPYOqkljVuX+KVXPLG4Yu8n1dMDycPVv6ajmYWJJn0Zp+ltorq90nbsO0kkm/JDA==