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
- 047c062026a9781f37341114db624ea2790af91bf7814ccae372be54dddcb343
- request
- 757c00f5e7f5204e61e119da25c141e9d159daf62480f90aa97ecb030d573f40
- transaction
- 4fe6e8c79575e56b06af26bb90d1f775cfe1ec1729c608beb9ce3ddb97cdb2ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23965
the chainentry 23965
- sealed to the entry before
- d1ce8a652ee5fccb2a091cd62259bd3f8d55135f368e7af745dc78997b74d4f2
- this leaf
- 150cd1b632ee8169db7090f06a6b622878c752ea3e47182dfe113ed8ccdc6ec1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hXvGZXLRnRTmd894Y0Z8QApG5pqc0S2tBhkAYAL54VW44trhBKDRGjhca37X9x6oItwntZBXjvG1Pl+6a4m4Cw==