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
- f9894de442414ae279e9432cce102308a727eb9ae12ecec78c95d5b1d76c5d75
- request
- e9c56f3a2e41bc4154ea5c7257db1de8eee281e7143722dc39eca205f8dfa8ee
- transaction
- dce4781c86b1cfc4d2bf035e11fe8c91903c6a9bf2d8cdf2d38662bccc1da9dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73118
the chainentry 73118
- sealed to the entry before
- 59ad565037410ab08cba4d1bbae41d6a2122a417d68a93241afdc4e18524ecf9
- this leaf
- d5568cbea262bbd6cfc396ce84566ec535add6a2a09ae4ba42ac7f0b75aff0fa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sB5dBdKm98PrGCKWHGyDPevra0k2GmYCYziLz9btNVdwJJwt3ASZOc/x6cd+ndjx9r/lSBpFbUF/lfiAQvb3Dw==