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
- 9c72386d023e92e3479db9ffa787473bc1ec33cc1fa644ac0e95771b5504851e
- request
- 36bedfb0fcb22447ab3ef45e04d01908e0d831cba939727b3021178d66d745bc
- transaction
- 2a0593a1c4b8d399fe4a1e5f88a7741be85e2f5e0814414c166c7312c6510fddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61335
the chainentry 61335
- sealed to the entry before
- 1ba28cb84e8e29023f437996180779ffacd75998c23e5db94d314211ca85ddc8
- this leaf
- 439485c59acc1407c25d94df0f7532296cf6754dd549ee9a71b94816007275bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cAPalt0ERfp4mZep0XeN3Arm7+EvJwsh3h+U6QCxBenkrqMxrWbqH4X+uacZ/7sxxcJjQEQGKIDijUP/5EZwAg==