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
- 301116d84b39e09863054209caf28de787789a2dc8cc9f73d7ef5a4ae8232862
- request
- 3c53d3ed836b13612767c56987407bb87349a1c5becce66045cb7a279dc198a9
- transaction
- 30aa61fe7c5d3c40ca33dd78e9c478efa9920b54812f7e789351f3833f2edfd1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33597
the chainentry 33597
- sealed to the entry before
- 372c413a7a4b4c15ba8fca2fd9cb5d97740927dcd12b78f4aa4257365b865b94
- this leaf
- 0d34f86ff0269fefe6715285652768d4229653f09e208d2b8e6f62c47064c1b2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OTVdjf+AQsvvDHpiAMILpvxnT1jAwuaU18bW0f4n0GiAjgvYDPWwcTke24MloDuJyEhsucO5MnbOdTJ3eB25AA==