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
- 5d20027b3f814cfcb9381c8fdb6a33b7df16ea544654a1d51eef2fe9ddf2b791
- request
- e67b59df0060dd1da1724df6a394c62e628cab6b2017852dee33be6e2eed49f1
- transaction
- be709c726987ab52efe82b4335ef5b30d7d264898cf8a3f279d89221264f4b50computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45880
the chainentry 45880
- sealed to the entry before
- 08e3fc164544b03541c7f83eeaff2ee4832a598809258db12cbfcb9f9bcaa47d
- this leaf
- daef242b07599df548ad2a0bcf641853f64b8efc73bea80f1f5ef0357a8bae5e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1RemoHsi2/jQju9TSpIF4Sbm4ghCbd9vT4gWE07AC1E4vLRKThiSpdm1aN25lsr+bukftHA93Yp3NgKyQ/IEBw==