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
- 47234fd73b7faace099933e914e9a18c110bbe0299bafbb64593ef757a87af7c
- request
- efa2f049bc11e1b16336e13e86739c32a283d635034089755af84e011f8709e1
- transaction
- d0f594547db74b5d660b67a3be8efbcb9e25dafa400fe32931598ef1ec254c0fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62874
the chainentry 62874
- sealed to the entry before
- 24afd7a3276c7c32d7cef8455f7c7cf1c44b622b9e2784186944f7b6f41d8d2c
- this leaf
- 636cf05e2f6eac6beda4146b3d182bbfb561bba570ae3f527343c438c135018d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Kt5aUOsI58VEhzDP3ymBeuzXbFfaMd2HZY/2cNk3BWc9R3b+AKYFKaRx85FjDiaMa2DMRri1HgL//nAjnJnVBQ==