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
- 079659bb0a816d44d62975f9ad490424ae7536562aea7be3b79aaeca924cca94
- request
- ff0f6b669b996910440e99cc5fafd33f10550da723624b19b40990d62ea1fcbf
- transaction
- 5c91c1d9b7d5135790c381a8483dfcd93e41391ade78bd19b28ed96e5ed4a31ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36200
the chainentry 36200
- sealed to the entry before
- f83cc7aaad78347448c1716bfaf2868dfa24916f1e6312ef1c0520ca46735d8c
- this leaf
- ac78a76456db467549446ed34aebfd7d26b287616ac8ec1b28441bac730c2458
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yBWrK3tXJNqihRTaZ72jxQHTkosNaz0GIRBm26DD6xBIAbibGL4ecTJyzq7N5+OvrfpYr6Eu2K7iXX6BapzSBA==