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
- e33156c3bf35bcf40a2f3dafc3d0dc3dffcabfa0b97688512c01630a7c4b4c6a
- request
- 61cea839362a5f1ca5885f1536495cc6b7b9c7133e6b571478887832982319d4
- transaction
- f8092ff46dad42ea5879664166943ceeecf0136b58180e156b0c9054d89caec7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61372
the chainentry 61372
- sealed to the entry before
- 3d04d6e08ef1c94070e3e14410e5f1e942a5cd66915f7e24822400dcfb70e14f
- this leaf
- ad1fdfe9b9829196a3c57720e8897b321947de984ff9784d62aa8137e314aeab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xVvMiHwEccp/a8/ikrIjjGRRj6FiF8rTuURmINpJDooY2/65/lzAyeqpp2TyUj4ads2RE0n1RnyOT9BV3khdDA==