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
- 31079cf25d9397be133ce318a14de46f7e57db6b67e1f04d599f403d42f6c67e
- request
- 30fafce171d5f7193b4062eb8ecfcdb87f375704cb79f00b22a133ad67901ba2
- transaction
- 97898ce90b904f3f01ea312683aead232519327a714f4167111cd0927147ab60computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17210
the chainentry 17210
- sealed to the entry before
- 8662b98f7ffad756b83da4f7d0af4a8aeff6be99df0ced582a51a73b747d3840
- this leaf
- 293ef3e886b371631047ca609c93167192812d6d0247cdfc648cd7597a8e0b25
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xUPM1VzCNW3REQQnVaWx/y9//SewbURGOKRysUN1tz0lSM6Vl/GPxrxcaZQSSdyOuLF9uYKAZpQEe0q5JuKdCw==