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
- 779154f54fe38efeacc96d35ea86656a31f05fd4dbde7927ab3eb2e52554dda5
- request
- f7225b7a38c8eaa33ed4041439fc4262c6d004905b1d3e6f59972db1cb1e4683
- transaction
- fa00f5e180e61d522f8d8e14377df80f7f446885be0484f10324ed934d747afdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21182
the chainentry 21182
- sealed to the entry before
- 597dbf685a592696e664f72583d44256009914eab40dcd635c2204072a3de4fc
- this leaf
- 5bf0ca199d8a67277e8424efe11a056052a0c5e411d64597835104af630cb0ca
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +VBRkn2iFxbrq2GOAHsSMDh2w5kzXzdJNJt8hBfle5qOylgPFO7vlQOrk5MEboapqp5a/dDsOn9zoGKRGHpUBA==