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
- c93202e093da1f63610fe1eb26b9a413fbd360600b28225a4643d8fe160e9de0
- request
- 90a171f6aca815732659fe6bc1cc9b0379933190500767458e660e67ec5e8550
- transaction
- 02c604ba140cd3a57e877dd5248da1e3cfa8c6cee41998844f5969e657779c81computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76820
the chainentry 76820
- sealed to the entry before
- 16128a691b5c34023b216d86a32ec2b94a74dd40d5a3998127aae563f8429649
- this leaf
- d2e2922f496e6fc64ea188703123e238dfc6dd6c732eaf587e2031db43d780bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xsDe1l6BEl9bRWkGjLt3RF+NAZS0uqSkDcOgdAlOANbhh6k2dU3Pcolt+pdjjmWcwsDdeVaOofqwFLfXKCkIAA==