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
- c92343e9a5d433ebf2f41982799d58c923321da79149861a351c00ee3ebbcbdf
- request
- 3d67a89b033313c37c3f3c41009fb1852af5b2814d9923f8851d79d17f00fc15
- transaction
- 03797d39b51fe1037706cf74d7ef4618adb74cb55bf74c9622d9b0713fd39781computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70467
the chainentry 70467
- sealed to the entry before
- 16f5bed29dabe142e9dc713f51c7266f74ba3360a4514a048497a8e2fad63054
- this leaf
- 6edd58deb3dae6ce0bc077f0a15f3c50168adbfc569de54c38760fe6984e7731
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9Mb1h4DeGiPwPmmUYKSMnp/zrxQa4bVKbO3YTgHy/qtoJ2FWEoxIcWsyS+l3w7fKHK/S0cFqZqkIxnNfuX1ODg==