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
- 041a549620ee0f0b0ac1e18bdcf5716edcae8eb33a034a4fe9f80dbc73a24b7b
- request
- d29cf07bd3171bddca94e79de256e4a8c40ab969181da2bbcf7e951afc731baf
- transaction
- 1e0bf6bb8677767b88af359a02e2a6285e56b5d1cb2f353bea74b2ac72b0aa96computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64722
the chainentry 64722
- sealed to the entry before
- b8f2e55d5c04cf3c0e66b77424445a5415cad2ec623a949866d7f9a54a8c2aca
- this leaf
- b5c88a408f52cff70e7b51ff2d28546e01c5a59393912832c3e61507ac1b80cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PjCSZW6icsP3tYJqsoksJcG9KsmGlukoLQy7mQgs+PgKaQ937T2JaNXVXdbyQ/Y5lTtseZH4t0h8bStWAlQCAQ==