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
- bbc9fcfb544ac1557e494d14dbf8fcc91ae56595aa9537639bc97760126348c5
- request
- 08c496496072be6278a8895f1038dadd87aa941ce7741ede9b499294ce42b5ba
- transaction
- 0725dca61d065101088f5300762dea67952528365a4329baef0488bf35e18332computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23043
the chainentry 23043
- sealed to the entry before
- 4ef5bf7dce7fb9b9f0bdba677a65b193ca3c8af4740cb2668420326e9497a9d9
- this leaf
- 83c5c6f78ab2c437b8a40a438803cc29a7e4bbfa5ff98ae648cb5845ab1a828f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3G8VFIR6mLD4S4M0k8/BGYkErcQYW0RlGSucd1dksHnH2CM2Pdemi/vL4ALiKENGVDxIXhNittmwsdLVFWsGAw==