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
- 73e8f881e1d3c10515348c43dab8f4373b19f1b0850d665c9dfce39d0b7702af
- request
- 7cd020c3b26ba852303a4990d8870b367b15db58079e6848828b784de00d051c
- transaction
- 9d96501e1908082ab116be15d9d626817105f43d8bdd02346419a2bf4d38c86bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26095
the chainentry 26095
- sealed to the entry before
- 3b2502aaf9beff67193fd6588cfd88eafd6b069135a93b525de51cfd96014a56
- this leaf
- ac35dccab141e25a7644c55763be25c9b267c8d09532324fd3de7bb15c6aff81
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wFhTzrDnYObWPmX9ETQMwWK5UTa2rG61sSMMkCf7bLVjaXcOiWfFVsxnsKSd8KtUT03rUvibH+vcmLLe+bvdDg==