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
- 4078da26cb503d67556d673bb6b2575ea30ce18a57ce9b0dacf3313127d279db
- request
- 34e9a8a7c9dc9b4d9f1c6f6d1271625c73284825c0d13dd52e7de117bd18f805
- transaction
- f1b78e570e43345158a089e32a53054d0ca413aedd6806836f90fe2f13b0c4b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15050
the chainentry 15050
- sealed to the entry before
- b4342a376afdd66f40eda14a094c7b85e16ae22dd2ac336ab1fd7d0d75023100
- this leaf
- 7cb7abbc70929b0e31cd792636123c5a784e65ec84b548c0af0cf84d0fb9d903
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EUIvuFyxaME93uYE5numrDPtCLgDbA2ar63VxQukdbvCTFJFq495FGqKT9GdiNJURw0rOXLPUuC52SNz33WKCA==