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
- 3d89e7a4e3b80f587d621395d9d96b10231aca5a0ef443555a459618c5277b70
- request
- 83b1ddc9690145a1bdbf98e378f500e427bfa71997296663859d282c9addf1fd
- transaction
- 3fe068259630474a7913caf019623b91c54e41b846bd85649795161f53feb063computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23227
the chainentry 23227
- sealed to the entry before
- fe70608e2863aa691d74394ad65c8e5378eee98f0f3989a68b835bc6924af8ed
- this leaf
- 7a25edb2d7a12c2cb24afd539120b03c375a77d12ffb761e7f421f6a42e9be14
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RLFNMLFM2L7IocqV729E89L8hW4CWfOdfjGtQ0N69JostSBAg7npleUk2LUGkQqYkL7Ipu/pLACRtPRrYJooAQ==