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
- 906e8edbed3dc063f8e7724706cfa1e5d331f0cee417e4b7a586da086beeb859
- request
- dc5212a271a3fff4162945142b313a8e08e26b2e46ba66294a302d951ea3556c
- transaction
- a13cf7eff1ee57e06ee05a0a2419891501e51dd25dac0398564ed2d58e0568b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44915
the chainentry 44915
- sealed to the entry before
- db5f0975b0aeeee7a85736d1f0dc9a4cc884787f71f4e028c036a35d1b18e12e
- this leaf
- 271242836526aac48117263753ebfd9adab5dc48cdb07d8c01308b7cc3f4c9b8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1OOCpoJqT4yrUqsKjZXWcGFoC6lx3WdgdRexiOtzoNn63zon0UV4adfVCq0c3xLE14eRB4R1f0sLqZXLmgcmAg==