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
- 2205c328cacc493735185144736b647ad8a8b847dfd8cffc40c7d19e3e91ae6f
- request
- 26edff9f882c38e2817a5d04236aa79708d8fe19a7718eea8ae7670373510043
- transaction
- 9f32a9bce675301bf75fdaee385e4a0be4e7d6687d3ce1308470e1b77f7ed168computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39502
the chainentry 39502
- sealed to the entry before
- 79ff04d9f50e3b2b296eff67be5b2f21abd0acf9d96aae162c3045e9a945db7c
- this leaf
- 47b6e00c41f6192a116eea3c75b7cc7cfc5a7c0cfdb6938417a90eab0225ce7c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pxfv7qVK6WSUhHO2Z6RmpgOdgtPjjOudZtURTMkQUtR6Sr5OWpALHPHY8V6zb2xVQWzPc/qPjbniq8fWrDv1DQ==