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
- 66f3e549b838276880a38ad5221cf3e28f5b39648c63ab24b5b6c964c626b4a1
- request
- f75493181b3da952be41dd9ef744bb82953126d4e5a9d73bf72e8535a909640c
- transaction
- 817b6258f342ae250283997dbc05f634b309df5e2423d025537ffc4921772935computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75416
the chainentry 75416
- sealed to the entry before
- 366eca40e87233ccaa1c84cdeaaf82c58318d4c81c91241a364096d7f1b45a9e
- this leaf
- 2ceffae020f40dfdd489923c4a13860396ce7217e5441b0188d56ad1ff6106a8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zo/5w6bGd/PYhjTKDpLs1zC0fHokw3rHG4TTvA9CoUPLkXG02u1mlDLmCVsc9xDI13YMfwIiNS4S3y7915TyDQ==