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
- 6fd474492be51101fbe27f594c4c520d83c9b0eced728c4feaa68a2b93bdf4c8
- request
- cc60aded9846f5db85006592d8cf8c7c93f383a10a6f37b65d2d303c3c035fed
- transaction
- c703538240a74c2d23de804dfa51096d48917b52d839de2f09e02f46325590e5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32448
the chainentry 32448
- sealed to the entry before
- d7d12548ef7c2af20d63acfd49ebce9e1f3ae0cd7d21f6b694e218464ad7187a
- this leaf
- 6b25c6d12b381b695fc1b2541e1c6a7de0fe8d53a2e0304c39e40f0a7c549157
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kUcKsL85KXO4zXXmV7ftVLr0or1irX0lAfs+KcCTVL5ylfr99mWUrYCa4xkdFg9QAisDWGCbi0qgCKBivqPrAg==