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
- f6494b887f4d9e97f2a0ffb0e81eed98faa6f71b6b8336ab23a5c9592fb37e1a
- request
- eb8c1d3bd5f066d0b71f263c074dbdf28098cd92194922ed6cbcf293685b932f
- transaction
- 71175861348c0727cc7fb2011f06b5ec91df214170cd9b426c490c3efbaa71f6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40905
the chainentry 40905
- sealed to the entry before
- 88d65c02bcda1fe35c51eddeed1a3dafe808efeab602a56c1818c7d18b65f2dc
- this leaf
- be9993231f93aef5c29f104fb72fcca483c6a944f73bea764fa687ab840af315
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RqPYQpvh1plx/6Rb8JWfqiD0ieHtYcineOVV2b+eTMZy/CmKBhpAquqvnxfJouLyMmrJtE0c9B/yOnG6MqYsDg==