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
- 8e510ce52d638c37340272416d0b6651100bf1a2a6c83b221ab3abbef1e14a96
- request
- fa93231eac55d58789ef97e40fe6f6cbb96400617e9513c6ca45a22e9bcbbff5
- transaction
- e0d5b109ac52aa7f9d87a43d6c698426b569af4a7ba9993439806c96e884fe0fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14305
the chainentry 14305
- sealed to the entry before
- bcd3de77f2decadc5800738dadbf0d24a237cac8f9fdf8981342c76143ac3ce7
- this leaf
- 68f79fc53ad2c73c365437b176dcc759c730a0af01cc69fde67864c033586566
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d92gaIMdifc6pRvBX3/2KIF05m4HJFAT/ElI/10LxX3j+D4MXnmBtT2ZTzXhnySzsY54UZOQIWZsuWZsbZjOAw==