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
- 41357afd6f3ec7113c8a67a43fef00684359d699e0284750b775b873e811a6ff
- request
- af5318cd4fe069bb071535aceedae5f490d67b28ef4b012fa474e6120257c0b4
- transaction
- 7ef1764d443977a6d58ae6af6778eb7bcce74ec4ef59783bff753342f7a907a5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32672
the chainentry 32672
- sealed to the entry before
- fdda16d807e0d2cf5e610dbddcddc3edcc38372e181975ba07ab4a5fdb29e59a
- this leaf
- 5b80ba08c6896bcde150604ac4c07f2acc51f00634a109bd2886bb317d268ebe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4O5tjzLY9byEyZFaCIPQxvhMjrndKVtX6iYhfu65zQ/xnIbAXBF0LdWFgy91OjMJFFc7wlnFAbkn4BItGpryBw==