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
- 284cc59c5c4f5e38ee1388326474e494b0f87989a04d1fe09bbac4e64f14f1e6
- request
- a88148a0afb2953692eaee8cda901f3f409390127023cd236cfdbc02291996f2
- transaction
- 54d6d56531914083e512ca44f745d5592b19465427e37169a9119a66cf9029dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26072
the chainentry 26072
- sealed to the entry before
- e7165785c3a70002badfd306ffe30c7e62e263ba3b0f4052f1a367b04dc77872
- this leaf
- 161eb3ba0dca5c14cca91eb68888c3e2edf31185ee511534e6cd83928f9c974a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XwLbDy+f+NXUVjroHCmdEViyuFlAulNrZcsFf4F4iKOhsikphhOvRFlfKmO+XkvU5MYgnoBh+zyQhGKQqH/ODA==