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
- 13f8e21147f2d99894aac72f43043962c6f8c9202a430ded65a7b2245a6c116a
- request
- 616ee11f8a8eba33390b3b0459f2762dd5b86b0147c613d2b545728c65319475
- transaction
- 50b7342f08899ad5245dda3b4caa55a77bb6e6eb6d6e14228f641910b067b8c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2730
the chainentry 2730
- sealed to the entry before
- d59f4eff2d7825c0cc8e370a106d552dcf2ca907a2decdc46c9fb920192d2c5b
- this leaf
- 8d9ce7b757de036535252ead93be8173aece849c853be8f409166df5ef951e3c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- x1IIu9pb4E8yMX7tQrnY0GDwp1fb4rQsa13XXA5/WP6BQvw5SrjV44W2wsQYTWU7GVqW9wajwfDIQBlbis7kCw==