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
- d82d4a9691eaf9e6f058418b4aeb785e1098dd69b71ded671a05b0404e2863a5
- request
- 70140f5e74a6efb70a80b3a275d0d234514945a4dccee786287124e218a00bc4
- transaction
- 3f273a91ce91af5d5f592a0580ff9c14e042ab29f1caa6905af96e633b17f324computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73732
the chainentry 73732
- sealed to the entry before
- 3f6226c823a4892844d27c57e889b4542558063eb1afeb5f2871f211c29e14c5
- this leaf
- ec8a9a9d9699ec5bd17e99b8cae182c0dd198d02187bbf9c786927749ebfe5e8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /hzQrcUoEIKwKFDvIiertoyyGvA2BQ/HiL1ysyPzyoZV9lCAfP8cwvixQvswVL6DfDMAX9PGFSXVhfOVHrb1BA==