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
- ee53b4116f5a1fb5e764242500eec14d2718cef8966c8dfb2b2586506971dad9
- request
- 935041c593a8907a6c1474b69115c650c162452049e0a3e2c66f3b68eebb6d39
- transaction
- 867be0fe4be106ea201917a76aed451edd71bb784d36ce1b043a393d1f393ae7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73650
the chainentry 73650
- sealed to the entry before
- d364172230dc092fc94cc0c0ca002e57f12ff81b08fcc09cba4b3259dae3474d
- this leaf
- b267dc6452254497ee2f0aabf5c6a49bafa5998f0ad30d001c1c8b2ef5d56740
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hik/g9lalGFxnnAAIVDDbOSRpaCA13hidEvyQjTGtagFVUTVFGqAv9xDyxCwMohtN+eEG/ee/vgOgrdjjmU2Ag==