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
- d04576a8e783b377a56ead1157ca75a5231fac17248c616c57ca70d275874ac6
- request
- fed2c83026f91859eaffc07962fe3242b81b14f531fa1c5e96a4ec0691e625e5
- transaction
- 4d6a1dcdda0c737e8ee177595e391d5f4f2de21c251c339f19ad343776b3dc91computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32315
the chainentry 32315
- sealed to the entry before
- 6ce13907584122aa01c92dc175d1a36661a32a8083e2598e5b466562740e8a61
- this leaf
- b54acb10b6aa8fd38e2c1bfdb6148d954096d6d6f9afbff68032d855c45786ff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Fg9NhEqz8EwHoOqEL5hZOYa4/r3aV9Ue9rvt2oZRbLiiHXnG/UlM73loTSlp+m8nWKyJT+XGB/GZYWhIDVhADg==