Payment Module Development for OkayCMS

Payment module development for OkayCMS

For when the payment provider you need is not in the base package — instalments, a regional bank, crypto payments, or your own payment logic — a separate module gets written.

What is included

• connection to the provider's API following their documentation;
• the payment form and customer redirect;
• handling the provider's response with signature verification — without it, order status can be forged from outside;
• every outcome: success, cancellation, error, refund;
• correct order status transitions and customer notifications;
• a payment log for resolving disputes;
• sandbox testing, then a live check with a small amount.

Where home-grown solutions usually fail

No signature verification. The most dangerous mistake: if the module trusts any incoming request, an order can be marked paid without payment.

Only the success path handled. A cancelled payment leaves the order in limbo and a manager sorts it out by hand.

No protection against repeat processing. A provider may send its confirmation twice — without a guard the order is processed twice.

The callback endpoint is unprotected or, conversely, blocked by a firewall — hence the classic "money taken, order still unpaid".

What you receive

A working module with an operations log and instructions. The code is yours, with no domain binding.