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
- 794894a1569c5389bd555ce3abe55c111891a43bc40681872df3e68302ce5b2d
- request
- 8ea4f01d9a4ee8f0552f630fac864eebecb1517f15e94911e3212a391fbdd24d
- transaction
- afa2600ae0db5786451345faa2c1c9ca4d9ecc5cd567e0748f091876e578dcd9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25447
the chainentry 25447
- sealed to the entry before
- ea3dc92c6e650ae33dbc218dc161d46b4eea8bbdc0f7996d81a67d04791578d0
- this leaf
- 9ac7578b5425f4d7633d9901a90350d3b1700de6039be160f143d5ae20771700
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aHocMGV03vnBODq+ltS3OwaO6m8lq66axLhm9x1dyBEbX/47JfQMFyfATPO/91S8RcK4HmGccMH50uwRayCsDQ==