Dchamplegacy Standalone Payments for PesaPal

Description

This plugin lets WordPress sites accept payments through the PesaPal payment platform without WooCommerce. It is an independent integration and is not affiliated with, endorsed by, or sponsored by PesaPal Ltd.

Features:

• Standalone gateway integration
• Shortcode payment form
• IPN registration
• Transaction logs in admin
• Sandbox / Live mode
• Success / Failed redirect pages
• Works without WooCommerce

Recommended setup:

• Install directly from WordPress.org (Plugins -> Add New -> search for “Dchamplegacy Standalone Payments for PesaPal”) for automatic update checks.
• Keep the plugin in the default WordPress.org slug path:
  dchamplegacy-standalone-pesapal/dchamplegacy-standalone-pesapal.php
  so WordPress can match and apply updates automatically.

Shortcode:

[dcslps_payment_form]

You must enter your PesaPal Consumer Key and Secret in settings (credentials are yours; this plugin is third-party software).

Plugin URL:
https://dchamplegacy.com/plugins/pesapal-standalone/

WordPress.org URL:
https://wordpress.org/plugins/dchamplegacy-standalone-pesapal/

Author:
https://dchamplegacy.com/

External services

This plugin connects to the PesaPal payment API (operated by PesaPal Limited) so your site can obtain access tokens, register an Instant Payment Notification (IPN) URL, create payment orders, retrieve transaction status, and send payers to PesaPal-hosted checkout to complete payment. This plugin is not affiliated with PesaPal; use of their service is subject to their policies.

Where requests are sent:

• Live mode: https://pay.pesapal.com (API paths such as /api/Auth/RequestToken, /api/URLSetup/RegisterIPN, /api/Transactions/SubmitOrderRequest, /api/Transactions/GetTransactionStatus).
• Sandbox / demo mode: https://cybqa.pesapal.com (same API path pattern).

What data is sent and when:

• RequestToken (POST, JSON): Whenever the plugin needs an API access token—for example when a payer submits the payment form, when an administrator registers the IPN from WordPress, when the payer returns via the plugin callback URL, or when handling an IPN and checking status. The request includes the Consumer Key and Consumer Secret you configure in the plugin (merchant API credentials from PesaPal).
• RegisterIPN (POST, JSON): When you register the IPN from the WordPress admin. Sends your site’s IPN URL on your WordPress domain and the notification delivery type (POST) so PesaPal can call that URL for payment events.
• SubmitOrderRequest (POST, JSON): When a payer successfully initiates a payment from the shortcode form. Sends order fields including merchant reference, currency, amount, description, your site’s callback_url and cancellation_url, the notification_id returned when the IPN was registered, and billing_address with email_address, first_name, and last_name from the form. The payer is then redirected to PesaPal; any further data collected at checkout is processed under PesaPal’s own terms and privacy policy.
• GetTransactionStatus (GET): When confirming a transaction after callback or during IPN handling. Sends orderTrackingId and optionally merchantReference as URL query parameters, with a Bearer access token in the Authorization header.

Links (verify before each release):

• PesaPal terms and conditions: https://www.pesapal.com/terms-and-conditions
• PesaPal privacy policy: https://www.pesapal.com/privacy-policy