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
- b4560c62b09082c078ea2ff1d6df5be7d4b5e16746558542fe26b2378fcf8a26
- request
- c30053e9e831f73a9d5eb29429c2ca2634386bbc7a991e0bfbb014d6d4bbeec6
- transaction
- 67cd9a182208c3708976f2f45ca25f9e6601638a1914f5052287af1205d5644dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47758
the chainentry 47758
- sealed to the entry before
- c9f8a76f4bd292717a7e9d633868edd54606202727dfd848cb73c8eacf10517c
- this leaf
- 6b65c57bb971d92558ecce94e09f0d6f18bf0e8241bb5cf09576f7c1a4665231
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7BGhMqnAifTyOMa94PPjoL0EeZxnK3SmrLK2IjqcUQFVoPdMjC8th8E5GVQJpODd9PRr8srtwAJI5boOzb12Ag==