Payment integration problems

Payment integration problems can occur at several layers: the DotwebApps application, the selected payment provider, account activation, credentials, the production domain, server connectivity, or provider-side processing. This article is intentionally gateway-independent because different products and payment providers can require different configuration.

Common symptoms #

You may encounter issues such as:

• the payment option does not appear
• a transaction fails
• the payment provider returns an error
• a successful payment is not reflected in the application
• test or sandbox mode works but production does not
• a callback or webhook-related error
• payment status remains pending
• an authentication or credential error

Possible causes #

Broad causes may include:

• incomplete payment-provider configuration
• test and live environments being mixed
• invalid, expired, or environment-mismatched credentials
• the payment account not being fully activated or permitted for the attempted transaction
• production domain or HTTPS requirements not being met
• callback or webhook configuration not matching the product/provider setup
• the server being unable to communicate with the payment provider
• a provider-side outage, rejection, or policy restriction
• an account or currency restriction imposed by the provider
• a mismatch between the application configuration and the payment-provider configuration

Safe diagnostic process #

1. Identify the payment provider and whether the problem occurs in test/sandbox or live/production mode.
2. Review the payment setup documentation for the specific DotwebApps product.
3. Confirm privately that the credentials and configuration belong to the correct payment environment.
4. Confirm that the production domain and HTTPS configuration meet the requirements of the product and provider.
5. Record the exact application or provider error message with sensitive information removed.
6. Review transaction, event, or provider logs where the payment service makes them available.
7. Confirm the payment account’s activation or status directly with the provider where relevant.
8. Confirm that the server can reach the provider where network communication is required.
9. Distinguish a provider rejection from an application-side error before changing application settings.
10. Contact the payment provider when the error clearly originates from their service.
11. Contact DotwebApps support when product-side investigation is still required.

Protect payment credentials and customer data #

Never send or publish:

• full payment-card numbers
• CVV or card-security codes
• payment-account passwords
• gateway secrets
• private API keys
• private keys or unrelated credentials

Do not disable payment-security controls or certificate verification as a troubleshooting shortcut.

Avoid configuration assumptions #

Do not assume one universal gateway, API key format, callback URL, webhook URL, supported payment method, currency, fee, settlement period, or refund procedure. Those details depend on the specific product, provider, account, and applicable terms.

If the problem appears related to domain or HTTPS configuration, review SSL and domain configuration. If product-side troubleshooting remains necessary, contact DotwebApps support with the product name, provider name, affected environment, sanitized error message, transaction reference where appropriate, and steps already attempted.