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
- b6d6a9cf9e5c86c614c478ed5927590bf6f4d6d3317f28db613ec01866568fc0
- request
- d32df99e32411452fc412638e9329b18cb695f33d143223c0d0dc242b2637323
- transaction
- 8a0f64c1b37754acefdfb6419a435b74d6410198e31d1d55b7780622fdb9f27ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70169
the chainentry 70169
- sealed to the entry before
- 35aa97593f6f90d2ca1daa42a585d849fcd2e3059900bd7ec405e3b0c3694062
- this leaf
- b938ea92f8f7ffac34d09f7744707a0731e5021e53dc3c5055e56ba8fa919029
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BesLWgmTZrpvcJEeFRnY0Ifoajf0D7kjYOPJsoPTOZgPYc1lFs9xpO56z8uainupeplO2WlbPMHrd3tHNDdSBQ==