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
- edbc693ed62112f051fa87485f40a7130e56e62aabed9fccff62c7f4b14a2d3e
- request
- 707d2de679c29797d3ceff53e6036f97f56487d54834c1ba428f163f6316553e
- transaction
- b14c7d6e90e7d6788b6c47ddb6df33ebea05b342806a0df96389a7f2ce65d0bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22489
the chainentry 22489
- sealed to the entry before
- cf453db25aaeb78a0b4a00b4dc238811b0f7124fcdb02163175d5372d8c98311
- this leaf
- cf43fbeae5a6199d640d8d4c33d3b94a3ffa76297f0fbd763aaba2c538829fc0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pj9z95xctgS7cwFG5KUSaw4JK+JcQGg0cCjWMDTqK65tjQzCxRjG72zTAYd9CujAXIfj/YlfPm58fbO1r4F+Cw==