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
- ae3867015ba3673e809602ce657854b52aa2fe00fa5e9343e90b5e75b02df92e
- request
- c7d72ff1194ae760979fb16b286b5a9e54dfe5394fdea11e5240fbbb0c011792
- transaction
- dc3a4fa1dbf903071040f6600d0c009238a7116ae9c84ea1c0beb10deeb68fe4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 566
the chainentry 566
- sealed to the entry before
- ddd959d9654f7c819a6a73d647be98ea0b48c941ee0ffe64dbcff78db532c625
- this leaf
- 4b3085e5daeebf2eb276cbe3d1a1263c17c7451d88a3e3495555926f8a4dddd8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bzpKQH5QbF2guHCKlYa77KV12gx2+ug9Jdl5ZIXLJIxCURhlrx8BXDfaxGjfYBf61fdOfrdI37tj1ZhK29LUBw==