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
- 59f35a70f77404f4f6e821ac117db220878d0251a2f47bba8c6c02f0ec5ce2f6
- request
- c344b474850adfd367fc5f76dba526a9a1b2ea4ce8ce52338fa9255fa6177756
- transaction
- c914a1fdf6bf14202bce6c701507757a51543cd44b922e8710ef965070418c6acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75817
the chainentry 75817
- sealed to the entry before
- 994ef6ebf6c9759b28d5b203d665999cb513d0b2b35adc570fe04d65d7cfa06b
- this leaf
- f3a3036d32ec60fc05babc338e5a1916e1536a3526d55ab755ca89db4622f43b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U1L+IFwa3e7Ln8kQueTRGM+1sruhKRSBFsw2brlakIzL6ZMQJDwydPdMJI2LpwWr6V1nUq1CypbX0z35qqiUCg==