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
- a2d7a1d3cb88296bbabfab9843df192b31ada4bcd643ee172c544c7c0b96d402
- request
- ed902b183ae35bb3a766ea43f4023bb3f4ee77dc23c6f9453e3f97ce2b805e5f
- transaction
- 384357e57201a8c2765f0263214f6808738478c03f2e85cf29501f8129b63216computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 491
the chainentry 491
- sealed to the entry before
- 9be681d75ec4f0fd7ba84c5799581f87d2e6c2846226139d15c4bf04b2140c66
- this leaf
- f607102d205812018cda401fa3c1e6dc34a2e607bcc5b4cae9517cf53d543c8d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AJRmZnc9tWTJWQhvlDjmZfp+2Q9T/W+nRC7YxLHkhLUevV1l1mhzQ9739ikpFqNUuEOeu9WKT2NtlT26pPCMCQ==