Scope the payment journey
Decide whether the website uses a hosted payment page, a supported platform checkout or a custom integration. Specify currencies, payment methods, one-time or recurring billing and any refund or order-management workflow.
Using a supported checkout can reduce implementation scope, but the business still needs to know what happens after payment. An order should reach the right status and a customer should receive the expected confirmation. Sensitive payment details should be handled through the provider's supported approach, with responsibilities checked against its documentation.
Separate project work and fees
| Project work | Ongoing charges to verify |
|---|---|
| Checkout setup | Percentage and per-transaction fees |
| Order-status integration | International or currency-related fees |
| Notifications and recovery | Applicable platform transaction charges |
| Refund workflow | Refund and dispute terms |
| Testing and handover | Subscription or usage charges |
Check the provider's current country-specific pricing. Do not assume a rate from one country or payment method applies to all transactions. Also distinguish a platform's charge from the payment processor's charge; both can matter under a real agreement.
Calculate a transparent example
Assume 1,000 orders averaging $40 and a hypothetical processing rate of 2.9% plus $0.30 per order. Processed sales are $40,000. The percentage component is $1,160 and the fixed component is $300, giving $1,460. These assumptions illustrate the arithmetic and are not a current quote from any named provider.
If the same $40,000 comes from 2,000 orders averaging $20, the percentage component stays $1,160 while the fixed component becomes $600. The total rises to $1,760. This is why sales value alone is not enough for a fee budget.
Add actual additional charges, refunds and transaction categories separately. Do not label processed sales as profit or treat the payment-fee calculation as a complete business forecast.
Test more than the success page
Verify successful and failed payments, interrupted checkout, a delayed provider notification, repeated notifications and a refund. The implementation should use the provider's documented confirmation mechanism and avoid fulfilling the same order twice when an event is retried.
Ask who investigates mismatched payment and order records after handover. Include a short recovery procedure and a clear owner for provider-account access.
Use the ecommerce development calculator to plan implementation. Its payments feature is a development allowance; the transaction charges in this article must be budgeted separately.