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
- 1c7e3ac269cdef829156b81b2407092b44d0939353df83dbc23a78fadcec283c
- request
- e44ce9b76b7e1af93574ed60b110fb6385d445b5392ce202c1a73b68aa175d15
- transaction
- 59f3e1d4f07f1314f82dc83e40d58bdaf82d21d854a2a7110ec8abb4440e7e48computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52474
the chainentry 52474
- sealed to the entry before
- 0714079249cc9701a7683aec207f211951712ce01ffbff55e3c269f6e783f9c2
- this leaf
- 7ebdc00861942203c0b7366344a8d69d94f2db5dccd34c7e879aacb28f4005b3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yiB8GMXTltIx46wWEygydolm1XL7BoLoFejWpE1sGbIVAxfw23BSjrLcc2fPfDUwuVHA0bG4glisOOCQs4wgBg==