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
- 6c6d6721715e5e40d67328f0a91beb25c7bd023b9c2e49378fbe62082737e75c
- request
- d1a6fc8c9551231b50284266bbb95c107244f66421e1faeb5d2917ab054296ca
- transaction
- a2a886c8002f9e16479ca543a798307fcb2ba203645a4308ca1479d6d41a5db3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58232
the chainentry 58232
- sealed to the entry before
- faf976f41fe45991bd425056b5c0f616728e4cc7f4391daba953a53fa95cfc68
- this leaf
- f69ea65fb19b046ba62473669a4771b1ad12de28eb0062cef8bce55b2c0c44ec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SwFHfp+2Hl54Z1EWkEH8nnNlPzQK68vdPMPdOFrxTQWcCKVb2FJxoX1hElCsjstrZUlCInqIEG6lb3QLxMl+Dg==