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
- aa0bba745d1f9363731681cc46791317c239f94bee66add0bc5e8532dfbadc46
- request
- 60f8796d0d00343f96ec62f8842d94741487adc64f0a2542e533a85ac589f72d
- transaction
- dce5f5101db88583987d30cb5aeba983104ddb8fb1f5c370be81277f870703b3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46233
the chainentry 46233
- sealed to the entry before
- 94536098bbab9b04c4cbd64caab9c15f7fcd392fcf5d0c163e9540401f0f87d3
- this leaf
- bc4f68265d593830bd106457197d5ada2d50a36eb422089c884171f7fcc2ea51
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- n0/eKJabNPNH2MnUKSIQzWMsI5biwkD1Y4cl61T/TszDoecvn1C8ZR947pCGHCFGCLSKo1Vov2tznyPCjPMVBA==