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
- 58c12562ce7ddf2180917c5906dbd8cbc897dde8ac974ca98db75bedae1f5a39
- request
- 2ba4e57985a51a1c450298c5966f2331a712c8425042e266e4ff39fe33b732d8
- transaction
- 3b61c4d6b65d595f09ec250585f1e293451877c519a39dad417660afc766c115computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53446
the chainentry 53446
- sealed to the entry before
- 04e4730a4689c1f7b7265fc2eb2d95381d7ba1d001ffb829a989dd2feaa81f52
- this leaf
- 9f13e229714be2519de057b4e13a16f21a445ab1e0cbc3657b1eda851664a7b3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /kvAeyzeSFkB+9Nqz2EDbDLyKo6vUMth07DQGTsQHV9wuR25l0C1GOe/29HmAgQVfqHJ2RGUmWVa+wPH7u8IAA==