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
- b3210dbe3e941e3c2dd78bb7c7c869d4ad9af39ea86991b3127aab71eafcf6b9
- request
- 4df0e011a9f6e69ec139053134a8202c7e6f62730a01eead22a48d16211c2ba4
- transaction
- 431fe2a24a6b2667b5c26795fcc9939b990397b56571b607c253d4bff09b305fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41927
the chainentry 41927
- sealed to the entry before
- f5f5cab59568a93df2215ad34b3279e6b86a17c6af95a198d0f5a1ca653d71da
- this leaf
- 72b86fae03e7cc498c366c2831c0f8e2f5feffdb4952a7e9199b1353af2b00d4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /yrtC9ltsuoGd6x6szsuiiAzBK9FaHbWFqWSFNfSE89k/DvP1VTXvlC8rVnomcpgNODyZtkqwwDf48zm6+UbCA==