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
- 1839e4494c5985caeacc7cf048f5e09897ca98af0f5dad294898b0159ed671c3
- request
- fe4e760c644f47fb849027ab553fe50b0986f9819d18f1471c0616a19aeaf55b
- transaction
- 067e73171ac540664da2cfaa18963f655e10ce56cc0f3ef8355967b5a006b2c8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56498
the chainentry 56498
- sealed to the entry before
- e0bbcbe3424eab4568e71dd95a3c2e3b4c415ef0b7be598d9bf790034ad9369f
- this leaf
- 0a5f02d889838a876e12017a410ac45038071bcf995b45f6ca5760c0e4bfb0ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /4OQGam1hG/gyu51q52qFvROQFsdhOJsxQth+3Anhrv1igbdiLKMhqCPNKeuGCzWncEQcFYdu9Jj11mq5GzeBQ==