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
- 96228faa4c9ef6edb27ebec453260bb7d11d857c67b89b73113898d9fc34b0b3
- request
- e47dde63b9f44fb0b0be792155ff743a4e7524939cf2105d045db69386e357bf
- transaction
- a7832c933eb8763ebb787fe96036e3f6bf2d13c7690f942bcd5b22a09aa38682computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66527
the chainentry 66527
- sealed to the entry before
- e992d0144c1bf9f40e876d1e1fa4ae934dac799bfe9fa64943101d648d4b2b78
- this leaf
- 2521d50c75d1801d8e3aaa39aef36a90847ddf39a4005b09ee15657c3cb57e96
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UDoTP3/1r+8uJvFafVnpBEE8cHXYPEyu+PuQEkM/qCgXuFk+lT8DYqHkjazmHGUzU0S55vQ6RzOiCAmSGZyZDw==