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
- 441cd3151879659935086afd0e87cb858c391428d528929ec794b3339eb61987
- request
- 31e1c3c1165e77555301aa74cb3dfc111a73acab0119c5e2141f2b1dda97ed23
- transaction
- 6847c06f34b5ccb7cde715925086d88f91dee30b6d1879a37bfbc4b8a036e93ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75298
the chainentry 75298
- sealed to the entry before
- 6b8994066d2ed9dc83bf283a5dc25c8146edf9ed348bb812255475d12f7a5ff3
- this leaf
- 832413c1bc4013c9b3566fd8f68ec28387e944340d2712ed929ff82818ec451b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VtExgrNqmeGB/lhczaX2Q6KEYG+aTjAhQmfrQs+Vf3TQ4AmMxyPTZXyZ4DPdxk3GGvu7srtsdG6I6KyoFf0KAg==