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
- 8edb1809f636dd7f289187b968d88f8a04a2f7ffccaf22499c3dff30783ca4a5
- request
- 59ae23449356da2d85fa440a9d89d8e7e517fe372dd29cc09d0e4bd1ce551556
- transaction
- 54a0738e76dc18386cd65d57de43af54376550dbdf922b14e4579632dbdf2e20computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13814
the chainentry 13814
- sealed to the entry before
- 8f17ed24032bc2c80623b86a7c6b41ce020248476c51ba7dabc6dc3ec92bc33c
- this leaf
- 641e6d27ce719c45577317e175d7ed511fed45c17c81507b68875d997b84b571
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wB002eTwuCthL1ULTKmjgKkufSIBoXU4Ca0gMqgmkHbpivd0GEwFmX5Blgh2VpxhCw/R6Sx0zzNkkXHf5CCUAQ==