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
- 3e26d9b7935c9f5529928a8aeaaf51264dde2c3b55bde9ffda2ba0025ea855ae
- request
- dbe9ad508db07e1d650003f2553b91bf18d6284a9d707b7d2236a99901f147be
- transaction
- 7b505afb67fef9601c4afcdd06d988a82b3a6619a8ba0afe96f029a72bc88d07computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9087
the chainentry 9087
- sealed to the entry before
- afb5bda34578eac4f84e03298b4ae5c976e016bbce30bbad0a2e6fbc81d23ad4
- this leaf
- ac08eeabbf064a2d35607950fd74bd2c79290cb1807f74b4ca367a2c92852659
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- o/9fJiG9QZARc0WY46Ap3TjSPfCJJ74SUMPPTdKGFqY4ejRCV+B2Fgc+dyZzcjFTYKdLq95INshkuzS/HvG6Dw==