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
- eec4eaf05aa965d06cd1759da5439ce7869b5f5c153b5bc742fa6e51f6a2e2a2
- request
- 00f233a05fa88a20ffdefc6b448149a5dec35dfbea40980fbff1419bfc3dc705
- transaction
- 949154e8c22d871c3a351be1630794b960e6518e88d1e767eb29a6c34c3179c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64696
the chainentry 64696
- sealed to the entry before
- d07df3331b9a3745f1d00efb86a1c19aec477626a341f7d9522c350a1a51e55f
- this leaf
- 2883584e1fdf2d80ccc52af54d98708384ce61eb84131ade94a9c4a04e3312cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lWOujI8SWsyTdoaA5GDm/1s6spY84o11n7s0pKvqVlyzoL9WpY4WbAx47UwGkoI60V62hAMHdPd+7b2WOesEAA==