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
- 60e6ad5396169c9cc64905bbf7afb8352bd1558c6560a61be43e100fe9e014b1
- request
- c88d69769c72df18a007bdfd4a3be5365c6113f83d73be0e684cd57a56ce47ff
- transaction
- 768c52d256ef5681758fffd12199f50eda17437ed07934891be4051001194d13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28793
the chainentry 28793
- sealed to the entry before
- c8fe07a1b6b7a39b139e15b660e652131df29c62f9584571fb43f9ff423560f3
- this leaf
- db3b4d3800ee296ae0f88f871e8a4a4612451fd08d2adb7ccaa166fdbd04c5e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Tb8lT8HsmFIST5zt1wM61z5m2oy8oJgy4qpuSbfsIAEPD7x2hwUMbMv/VCau97iTp58Ka1TQ4YKHOm6/D2yrAA==