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
- 2d0f2cfc4120a0d93759d89f6fad1d88c13979db100432e80f9c9e231cc131d2
- request
- e4e9467f267bf42e74625150c15330532d05d06084725382b24baebfaa8885a0
- transaction
- 7a3442d3dc6195dc25939c38c1384179e4bc114c2259a104d1c623826de5b080computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41327
the chainentry 41327
- sealed to the entry before
- 7300028daf81c05deb03d6ec0763fda07a833b52f7b0aa61516b909cb7f6a7d5
- this leaf
- fe2ee4b91f7c880c98c261f9752aad6564c48c9f1812822196f6ebaf86e9b5bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HIPwmwkkmKF75/MRjDJLZ6u6mr7ZCE6pPQKaTbMo+YHH80Sq6pGqm6kY8HnfDlbiTVMhta+ksvQ3GnB0F9eTAQ==