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
- f299048eb13114027369214dcc6ec71e2a27193d91ec99287f8ad09be8782790
- request
- 1e89552db889ee0652914414c816295682a8cfb1f5465d2b5c25b440c7dc046b
- transaction
- 297a7e02daabc1078eed5e87d45b73a5faf881922a9f773aaef595e0cc40bc50computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35619
the chainentry 35619
- sealed to the entry before
- 842328317178a425832857b20ed41ef7891cf3b54e236c54d7d892356dde5ae2
- this leaf
- 9e39a220612990d93aa144580098d8abf90f27137325d517e18b72d21084516d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iZjgKky8tbUzzBwk3gEUF23j8K8HYQw54Hzrn6vOf5L+bceCkFJYKDRDvKRl/gxqWSx2dBW1kxdDcGcfBFB1Ag==