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
- 6009f2c98f5893d4c58f253bd3d0360d4dff0ea43804c515c3a6593842914ac6
- request
- a286645754b626a6a132ddc4b6d59ef710db4e4685d76fdc1082d5bead26c9f9
- transaction
- f132cddbc60d390e40eaf58291fc79f59d8b7c712b5f5c843c0ab9763c752115computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42578
the chainentry 42578
- sealed to the entry before
- c750e20e79b1708621c6a2840e5adb7efca497a30bd47aacc1664b49af5a635b
- this leaf
- 61dbc09a858a4401aa226eb95130773621a5be0e9aa26cc620baa7cf2c786353
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ymie1D0vr5i5Ge0ki9BRojII0GX0Bro6z8X0cAfgBcH3sA58p9snX2A8gT0P60xU9Vl+HvlxJ1AfYKsnrStBAA==