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
- 9ea39a53a23832c8123da4110658d9d1f80a8d7bc792053f70b02d80c84b66b7
- request
- 090769854c749d87f266c6487ec2f698ff71f5fdc5762fd6a736f906b48f103c
- transaction
- 861cb63f12890cc5e5de827b7b42344f47777dc7390defb012bcb00d09321b68computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45793
the chainentry 45793
- sealed to the entry before
- a98a10bdbe9ba2c4de15bc44424fbbef7e485f538b4286406e4c376f9ed581cf
- this leaf
- 400ce20f3a3db53ce8ab49744e142106fd086cd72f1ab34465c6b51ac32a4e5c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AbbL2v2RbNwYwhJYX2XPg+HDGIx3uKcaAz8MKu1VAFohzCWShPiuIGBhtJq2pmypr+VG7y9I3bBhonByChOJCA==