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
- 79cf73e6877145732ba21c853b32e0a5f716ea265a55043d2a373ebb73de5c29
- request
- 83928e10fd80b1fdd64fdac12ccf0b8807ea65f126292088aaf9def6448ecf2f
- transaction
- 82c417128d37f9c9aefed798112900cb9ac13baf251c7cc866005de350c89a90computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18787
the chainentry 18787
- sealed to the entry before
- 332c7f05d2a858cd5f87746d1c92c0ae6bc7f0404de07931e18d54a55e277b4c
- this leaf
- c5c8118e0f73b67e95d1ce13ead87c7b9c22f61b64d08dd6053d837e36f2f312
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cIGoCbBO4lExCu8Daj0lS/hURJbbBOj4Oz0zzAB5Hi+wOWRfC39ykwidUVHU10T+cpw11Z2m3m03DT+EHnl2AA==