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
- 5d4d5077b6b67ad7d962a4b051a00f7d7a6ecd2e1563f2287b1d9c1df96997b5
- request
- 5513f1934e009c36142d210882b9a4053fe2bc1c8d3c39eac8da7252db26ff50
- transaction
- 6d6b09268ca096c17876454f699767457fef5abbf619e090941041ca74ecdaf4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 661
the chainentry 661
- sealed to the entry before
- b61a318b591636e203251408391f7ec22d2cac1b1170737103c20ee713c86581
- this leaf
- 7d4d961783ad56c8a3e29b57e7ae8c03807c0238d0dce514af4543e9ad44df99
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JAgnY1xfaXS723eBtBsgloRcJm1FsQHJ0PLuDrGC7p/sOqaxryAjaiLdOXxMdu5NMQjtRtSPZSut8hCAGw2WCw==