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
- 7d0433250c14e4fa0ff557e97896d8c112f3e599e4d0d3979773efa889adeb6d
- request
- 6e814a104fb1238e5b73e53b1a8a99a2e5c56e987a856b640a7a6470b5b1c826
- transaction
- 1dfb837b1dad5ca349ce0b86ea485f41276c417c8c21149b1604940fd9fc65e7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70250
the chainentry 70250
- sealed to the entry before
- ce5fd4992aa8cc0a13f5cba8eb29c52a6dcea3a6f420082c625f627bb0c90c42
- this leaf
- dc58352e7185c1e2fc84f7f00e4b884fed4f4815f28584d50d0c4a4e82ebc367
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Fz3WeyAOnh3gj2Cs1amKGxhKsPGxeQ9U7iA3TzoMZYDX/CivzIpkWerzSC8rKtp2sFH+0lOfs2+vISdDApXmBg==