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
- fd41aa47db1181a5db996094a50d339391f8eda5661f7e005152a6cc3b1c538a
- request
- d663b6a8335ade3d407b4c46781e165f619a31eab7fe09b94e54b3e2edee8dbc
- transaction
- 978aba9641044fc9048cf3d470b14eb6f08e65110946499b456b736545295c1dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9820
the chainentry 9820
- sealed to the entry before
- 58aaae3f5116b453da7805e9c357ea4710ed61d02c09d9ab2b41720b74f4112b
- this leaf
- a20656ae7cadf7781dc2d1533da61bf959c6ecdb1a1de2975e7f37ed146f3c8c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K4XkYFjCfsVLOkq2sVrYptDyCn6GKg2ZWmUUQfwUU1tM/bPsO/hOR7Kd74gdaQ38zij6WehmBF8wiRSuVvkQDQ==