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
- dc21ab23a34841ea71277bff1daaf5554c41e9807d691d785a9f7dd5f33755a8
- request
- 9d6d7af75ab9ea76d3a7621480a8c1dfdb1fcd9b908f266788e635a26cd85e5f
- transaction
- 256156bebd8968ec6f8ecb9d1e663cc57c5bcd8c95d6ac63ff81bf590a34c8b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36006
the chainentry 36006
- sealed to the entry before
- 8c444b74768a1a8a10b6e6cfa1bf8abb0b9a4538032f406ef241368f7f4e9aff
- this leaf
- ea76b9ef8f5160c569e6f19cc62de3ac4ce300abf130d5dd6a61679444374105
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 78VtBvi5c3jJubKUB+cpzuaMTJp4KnEgz44ESBv1ioW7ILVuFbahWENaglKHpPM8S7poisENJJO42kSwAWzMCQ==