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
- 3300d2a5df6c366984156d32cda7d7ce330665993ddbfedff0f1cd63112b36a9
- request
- cd2ae50fd6aa437a28d144c98e2066750c4945a72633bb70970c2f9c715e0a64
- transaction
- 11629d12c4c69d793d8a2b94eedb15169e42229997994a988a75b6b302deb457computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29568
the chainentry 29568
- sealed to the entry before
- d0f89d2359ec544ca9ed623491d8131f0af1b5e6147654b9dc277f35d990951c
- this leaf
- acd0787c8c7d33f6c5ee22be0240e780299570f30f9b319c35ff3fe68ddf7bec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0N8e8M6SQqXLp6BrkiExCuWYegai0xFkO2Cu9gvkDb8Z7SKxi8E/Xnh5LTzaZaHqszdsnqbkHTCCSLNVN+NdCw==