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
- b73eeac2322e24747ef719e3c211251ffbf4b781f1d30a7423a8efe42baa6b91
- request
- 27c1e6a54305a3661a4389a0f3a703cb33547d26fbbbdbba59a619210e946b54
- transaction
- 9401e44ea79d8b509eccd3f2ab928b068e90147af1b2f96ac84bef9b4ecbf376computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11438
the chainentry 11438
- sealed to the entry before
- 488d93a0abee2dd4280d055c7fc2d6df0d526296c541b12f844d6735e2db3b26
- this leaf
- 94dd0aef6910fb440420bbab5c3ddf0a4c75f215540c8f75dc73be937ca05a4d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TUlhTNNaOTjI9Q5CDOXSHa03Fbqg/R99fdcK4TNTA/s4Ws6BYlyIijaxxE5RUlxp30/kb6ifpiSm3xx9sbiABA==