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
- c4be2c39496abb41a704b6ad707f53d9fb2b66322d41c3ffdff402acbbe03f56
- request
- 6b6f6d95b5797cc58ca404f86028e55107c2554e4bb5a52e7857a343fcebbff1
- transaction
- ed25a7bd329c6bc242849dfc315e748aecea57cef3f8e45fe76715d4b8b840c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61800
the chainentry 61800
- sealed to the entry before
- bd0c2bd6c01a995320d1eac16a4d08dc5ed9cc02d2cfad1ba38651422ac48b10
- this leaf
- 63e8855e81f2d6681258811b52c9ba8eb5578c7ff785316801fef4bb351c4737
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X153mbmbUJxZkTmywVmbcPemh323uFl9fTL4r6JIqJtJRHSmGuyWzTavW5ZObJyXeOXkbripGIqw49Tm1qKbBQ==