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
- b097f201ffd6e97cccf85dca2de8ef26c8ae1a221d83ff1ba16c37d1ece467ba
- request
- 7ab8efb85dd1ee399e215b9cab99e96a91557db82e3ddd1c11930d1d1494c588
- transaction
- 65bdc3995fbb6a2847dbd3c705aafa93bee52dc378170d72e44297685d47f6a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10201
the chainentry 10201
- sealed to the entry before
- c728cd1bbf0308f15303b6dec49ed5e019f7fbc00e65d64f7af54d7a81bab0fe
- this leaf
- cd101a06414b88a870adf809cfe359da795c5e767e60d3a2dab0572f2b280213
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Km6nH1hF73KBt84H3N6/LgijV3Ajm6lHPUGcEt2UXI+MuSrrFi9XLqoJ2tSrySltIYPJXkhDXr/CTNMsW15JBw==