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
- 2d00e2c005024efc0c57675659535945779136bb4f375f54a4801cab222dfa69
- request
- 6316d749876f283cc89336a7caf5d3cc2673c6bd2a459436015a0518cd38d0e1
- transaction
- 1c758f13b1379fc409b6cc6729f010a24b7236cf8088d64325467a2cb60c2ac9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59679
the chainentry 59679
- sealed to the entry before
- c7d02ad89a39eab1a3947f86c09fc5f1156a06572ac25ec11b89277ea887f90e
- this leaf
- 497a3d6cfa95003763115c17e040f3e1c74bd2a27cea609f71702c78905d4852
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jEeBL20Z7GtmHW+FFM15GCNr9VpNko9TAV92DJLSwVAWXEFihue3Ug5X2yVO0ljMtCxIESuH1yESPX4iMIaOBw==