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
- b4290e3955b9ead694b7ff41171b98c2c5ae235e29b43f0d1bb58c89bbff0368
- request
- 43d154afc12353ef478652e9c4915f8a53bbcf297bb6496af7df080b4cd33ae5
- transaction
- 9919514e5ccc6fc2b20630b72f5cc40066e2bd1fc32a14b8cd74d8b40780a803computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27940
the chainentry 27940
- sealed to the entry before
- 21f569e643167df9a64285441eda87d3af8aa002a0b6f7a2cb308ff9c40b5900
- this leaf
- c02d752859b4b90e74a615a028b6e0d1a156a6e3de3eb63d6bea5578385cbf99
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d4x23nVo1f2HwMWHZe+CalDl2/+f1gB9X0OSDJ/zQ7ddSDvsmiVhQA3ifR2jZhIMrRbONtJWK1t+CcV6JvJfCg==