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
- cd27745fc9c2af268bb37ff5b9a163bb28d29ad6fc74acbd9f3c367561c4e449
- request
- 3db6fb551ba49995fb240b6a08eacf402f1f7df3f72e54feb4195a353b849f88
- transaction
- 411e2073f5f675bb4023fc61d98d1c185abaaff8b7462b172de63100a20290d0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56483
the chainentry 56483
- sealed to the entry before
- 819cb619a197b8b2f6f32291787e97075489d58a37fb568600f3d356668d05ff
- this leaf
- f8564574b989f643355048d21ea482845a526976c035cd1815679ad41ed15618
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- verJFBtLklss+1V2dtptZtlBO3OxXIv6fEAr73Mt5fqKqagOPj80Kkf3euL589ZERRVuRMz/lqPDSXSljTyGCg==