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
- 85877577ce6d75fe7e735475d71dfed90d1ab0ffa3ae726238400cf6f40583c6
- request
- 74122aeb8999b96b55c9b043f8efa88f5ca4821d4363a598a149d89f48a87d90
- transaction
- ecd79f19309a0cfecec612fc7baddfe4032bb6fce9ba558112c7162fe0c8599bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40134
the chainentry 40134
- sealed to the entry before
- 0ac1bb03513a8ee923aec546700d1ff5b92b8e989b9e70402619f4702b06be15
- this leaf
- 5db48b5e8a6a1e0b27a5dc34bf474ebb5c4ef8f5004c8e23400c70bfdcf01410
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EAaObqig2KcgfC8TDHk0XXV+hphKNLPoSMId6WOr0PNXIu8Oaeaa3HiyVwt84t6sRE8mHeg4PB/wDabLw4XrCA==