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
- 4e3e064386bcfb2607bff299c2d789305c6bb67215cc0d1023aa10c633ed4ac7
- request
- 736222e347fefb61214a96a0396ab2c848a3a979483142878f0372845b2932b3
- transaction
- d75470c1b44727baf50f2a29c5ed20ac48927de9f35b965d747296adb5cc4a48computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23134
the chainentry 23134
- sealed to the entry before
- 17f0b6c50b4b9998e070b59453a522c97e2cfef3ee3a8af8b7fba279ed29a5ef
- this leaf
- 060c443500619a3dd2f1305662938ee0d90e1a02aee5d45e1e141bfbf33a7e03
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Z5wRDrwGyl5H0d4+D2yu2lfhxPUjxpICLGz8YsPJ3S6QHAdxemeNmJYyRtQStTEpBdKHXYqCGiwWgmISi3bdAw==