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
- 45097a46ef1874d05cdbac82283c69b7fe6c2755faf98dad87a825e867382a37
- request
- 8b696b03f51d73c4e3781f4a495faff1e748501781d372843c43470b16fa49a9
- transaction
- d235cc3721aebbc4a9381b4c0f9f8a822545bf999c2083da533206fdcecf30a5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1640
the chainentry 1640
- sealed to the entry before
- 9e49e0de46d436de3d6534c27c3db5f30016234372827fa17cf18cf10daadf3b
- this leaf
- 8c9c4ba92d22e1ec391dc2a935b7697bf5c1ca1f9dcd11d96e609b8f018c8242
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- n09uHlU20gmHuJDfZCT1nCRnssn+ZVBQrlWluEFuBLm3i5WjlOZQNPXEtQOCUI5ZVilxCVdpE28o3hzC7FgZAg==