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
- 9a9ccf7a5d99c8e8221ea462a527abcc40fdce235bc4242c57f28010f241fa56
- request
- bc9e5cd8579afe89a024d445952b4b57927ffded04bfae567cf49b9bd33be322
- transaction
- 34ef9d8dcc5b67c4323143d6bc1189dfc572c8bb8329fca3a6166a21a5a8a462computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36952
the chainentry 36952
- sealed to the entry before
- b2f663d4d1379773b9a923a90774c0b8f11d5ea1a1ef3094523a7fc6d6ec4a7c
- this leaf
- dc099e08c39b38315a2854589be840e0856077bd686ca9eb888a0117a55e3247
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- E7D6uYoG46fcSR6btQmzB9U95oBD0xtiXwe/SdMJ1MuWD8nxcmXrtKKJCR1AV+QAvF4Dt3ydrc7rP6ZX/WKcBw==