Configuring Stripe in WordPress with trtPay: integration checklist
Updated technical checklist for an existing WordPress payment integration: test keys, secret handling, webhook verification and launch checks.
This URL is retained from the previous TRT website. The text has been revised to point to current official references instead of reproducing an older interface walkthrough.
Check the installed integration first
The historical article at this URL described a trtPay settings screen. Interface labels and supported payment features depend on the plugin and version you have installed. This updated note covers the integration checkpoints; it does not claim that a particular plugin version is available or supported today. Confirm the plugin’s own instructions before changing a working payment setup.
Keep testing and live credentials separate
Use the appropriate Stripe testing environment before processing real transactions. Test and live credentials identify different environments. A publishable key is intended for client-side use, while secret and restricted keys must stay private. Do not paste secret keys into a page, a public repository or a browser-side configuration. When moving to live operation, verify the account and credentials associated with the integration. Official reference ↗
Verify webhook handling
A payment result may arrive asynchronously. Configure the endpoint and event types required by the integration, verify webhook signatures, and ensure repeated event deliveries do not create duplicate business actions. A webhook signing secret is distinct from an API key. Confirm successful delivery and the resulting order or subscription state during testing. Official reference ↗
Test the whole customer journey
Before release, exercise the expected successful and unsuccessful paths in a test environment. Check how the site presents the result and how staff reconcile the corresponding record. Include the cancellation and refund paths that your installed integration actually supports. Keep access ownership and the operational handover documented.