Segpay Merchant Docs review
Segpay’s public documentation is where I’d send the person connecting a website to its payment system. The useful bit is seeing what the website receives after a customer tries to pay, including what comes back when the payment is declined.
Read the postback examples with your developer
The Processing API guide covers payment links and postbacks, the messages Segpay sends to the merchant’s website. In its table, read the transaction type, action, stage and approval status together. A message marked Sale can describe an approved signup or a decline. If I were still choosing which tools to use, I’d start with Porn Webmasters to make a shortlist and come back to the provider’s docs for the actual field names.
See what a test payment covers
The testing guide describes simulated card approvals and declines. Both can send a postback. Test mode marks those messages and doesn’t support rebills, refunds or voids. I’d keep those three cases on a separate checklist so a successful test signup doesn’t get mistaken for a check of the whole subscription.
Anabel’s take
I’d ask to see two outcomes side by side before launch. An approved test should give the customer the expected access. A decline should leave that access off and make it clear what they can do next.