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
- 31e1fea74b1a035c53406ba6de2dd82fede1ce97fe21476e2eecfa560db6a88d
- request
- d3dae094040772b816a68daa7d60b32fda1764589005936071e16979ac8dc58f
- transaction
- 766eefbbfd41b8f39ee19de4d0e6316c863ccda6d4849e7cdb662a657add42d2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52099
the chainentry 52099
- sealed to the entry before
- 8598db869258cb5863c7e23bbbc38c854996c29483e89ddcd2f6e8b18539eb1c
- this leaf
- b0b6566c602a46cfb0ac9058288621c0046ad018b4e53523a1903da62c1693be
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LbMVdjztO9XiCIA1ju6JNYq0iMMDnRNnQmVyjSeyRaVigVQ5rAqLN/EZ99yXQ1nezxz7L2xwovcZiV4FgoN8Ag==