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
- c9270e285a8014c1ca197390c33e1de4c679239c13b149596a361a7cb16e1b1e
- request
- b42b6f12d8516e434c225089699c1dbf145e20518775ab0d0d512e33f81d30a1
- transaction
- c7f893452cd0add5bd5f4aabf3ca6bbe060faa48ba3a33c06f71e7543388f78ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38143
the chainentry 38143
- sealed to the entry before
- 52ba8194d208ce412c2d77480d65ab200f3e83ac17a532335721bd563fa2584d
- this leaf
- 2db00d0c1639ed9c8fe06094b80aaa2856bc1a5d44b54b262b06413f7c52c967
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PCdqEkHacfRfNCZas5nZ1ewEj75aJTeAOkVYHWfH2xZidplK8hnHnrJPcB/5R87eexFzklRJRCyiOjp2dXrPDw==