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
- 6474eaf4f039be175a86c6019df680068d07491faa6c6712c0f3afcf2dab25d6
- request
- 050a3fe4d8d70c5925a605296d89a0e3485e731528bc0707518a820bbe2bea53
- transaction
- 996e637a31f18ada21adcd6da068e99e08a4524356e3f81769da794bcd1a48c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20060
the chainentry 20060
- sealed to the entry before
- 231d8c9510ea9119ee08180ca8957a79c216ec90879e7de7a8adc2344d5d47ae
- this leaf
- d2b08590668f6ac10ea755b07f175626481860b9184c93390a3c002d641d7473
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LBGmzSsFE1NhY9daTZXXDsvYthFz9NsZUK6ZKVnV4ev2oOKTZdhcqTD1VEM2qY2uxn/kmuQYyzZzC5WyBP1JAw==