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
- 5f9204b78f8fbdc4d8d3e68ee458b6b90563a560ee97a2758279ca6bd27016c1
- request
- b9ecdd19538135525abfa8e852db6443db317e2c09f12fc0f5bb733ea4ce63b9
- transaction
- 6899e01c25aef3d1798e9001f127b28d8d609ed9fec97cc50502398a95d8c922computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28819
the chainentry 28819
- sealed to the entry before
- 662161c97c8a37a5c0e3cfbf1061b71ca7acbda7f11a5a0197acfb5b18ab8ff5
- this leaf
- bfbe8180118eb53528aa9f6db3a008ebabc50a2132cf6ae8aa901368fadcd8fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ww+DbD3xUjJD5peaNVbrzfUN/3gjfdbG4wPEgUqpNO/6fK67h6suf7n35E+0aALwB3PDyiC8dz5E/K5rfE6OBg==