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
- 40a55e16b66fa303b0595cfac4b2e26ed2762ad6869544316ffc13a4b89cf6f9
- request
- 820fc8b935c7df421bd7eac7cbe958c0527f0986477ee16ae63e0be1a6f65d60
- transaction
- 38a697c07d7a65015a6933165871175db047af72860a0c0e213ac928c4da48e2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21756
the chainentry 21756
- sealed to the entry before
- f38243c24962562b37ea9c7b73b55885b6590e05e2914542c266ad07ecf29a46
- this leaf
- e8599a6f903a1f693f04527c667d4113b0a4911acadd06c358309de7b6d96c59
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- s/6UkmKyyX2szyQMyRVXKxE2xvzyJ8EmOdajWGxZDMCe5pWgRXuoaP6Ajoz2CyN3Y0bk2nAsoirmNRErrTWuAA==