Schedule Your Free Demo

See how Shilte AI can automate your enterprise operations.

Payment Integrations Tutorial | Configure Payments in Shilte AI
SShilte AI Learning CentreGuides for setting up and using Shilte
PAYMENTS · SETUP GUIDE

Payment Integrations

Learn how payment providers connect to your business workflows, what information you need before configuration, and how to prepare payment settings for testing and launch.

1. Payment integration overview

Payment integrations allow a business to connect its payment provider with the digital tools it uses to serve customers. Depending on the provider, customers may be able to pay for products or services using supported payment methods, while the business can monitor payment activity and connect payment steps to its wider customer workflow.

In Shilte AI, the payment configuration area is designed to let a business select a payment provider and enter the configuration information requested by that provider. The available settings may differ by provider, account type, country, and whether you are preparing a test or live environment.

What a payment integration can support

Online payment collection, payment confirmation workflows, and a more connected customer checkout experience—when the provider connection and the relevant Shilte features are fully configured and operational.

What configuration alone does not mean

Entering credentials does not prove that a gateway is connected, approved, tested, or ready to accept live payments. Complete provider setup and verification first.

Important distinctionShilte's settings interface offers configuration fields for payment options. Actual payment processing depends on provider account status, correct credentials, backend implementation, enabled features, and successful end-to-end testing.

2. Before you begin

Gather the required information from your chosen provider before opening the configuration form. You may need to create a merchant account, complete identity or business verification, and enable the appropriate API access.

  • A Shilte account with access to the relevant business workspace.
  • An active account with your selected payment provider, where required.
  • Provider API or merchant credentials obtained from the provider's official dashboard.
  • Confirmation of which environment you are setting up: sandbox/test or live/production.
  • Currency and payment-method details relevant to your business.
  • Any additional callback, webhook, or backend setup instructions supplied by the provider or Shilte support.
Do not copy credentials from sample code, screenshots, shared documents, or another business account. Use the credentials issued specifically for your merchant account, and never share private keys or passkeys in public messages.

3. Understand the payment-provider options

The payment settings interface includes options for M-Pesa, Flutterwave, Paystack, and Stripe. The exact requirements and payment methods depend on the provider, your account eligibility, and the implementation available for your workspace.

M

M-Pesa

Mobile money configuration

For M-Pesa configuration, the settings may request values such as Consumer Key, Consumer Secret, Business Shortcode, and Lipa Na M-Pesa Online Passkey, along with a sandbox/live environment selection.

Prepare: the credentials for your approved M-Pesa Daraja application and the merchant details associated with your shortcode. Confirm the correct environment and supported transaction flow with the provider.

F

Flutterwave

Payment gateway account

Flutterwave provides merchant payment services in supported markets. Shilte's configuration interface may request a provider API key. Obtain the appropriate key from your own Flutterwave account and confirm whether the key is for test or live usage.

Prepare: account verification, the correct API key, merchant currency and payment options supported for your account.

P

Paystack

Payment gateway account

Paystack is another provider option displayed in the configuration interface. Its account access and payment-method availability depend on country, merchant approval, and provider settings.

Prepare: the API key requested by the configuration form, sourced securely from your merchant dashboard. Verify the environment and any additional provider setup requirements.

S

Stripe

Payment gateway account

Stripe is listed as a configurable provider. Availability and supported services vary by country and Stripe account eligibility. Check Stripe's official documentation and account dashboard before selecting it for your business.

Prepare: the requested API key and the required account settings for your intended country, currency, and payment flow.

Provider availability variesDo not assume every provider, payment method, currency, checkout feature, or live transaction flow is available in every country or Shilte workspace. Confirm the current provider support and implementation status before relying on it.

4. Configuration walkthrough

Use the following general workflow to configure your selected provider in Shilte. Labels may vary as the interface evolves.

1

Open your business workspace

Log in to Shilte AI and open the workspace for the business whose payment configuration you want to change. Confirm that you are not working in another tenant or business profile.

2

Find payment settings

Navigate to the payment integrations or payment configuration area of your dashboard. Review the available provider options before selecting one.

3

Select your provider

Choose the payment provider that matches your merchant account and the payment methods you intend to offer. If you do not have an account yet, create one through the provider's official website first.

4

Enter the required configuration values

Fill in only the fields shown for the selected provider. For M-Pesa, this may include application credentials, shortcode, and passkey. For other gateways, the form may request an API key. Use the exact values from your own provider account.

5

Choose the correct environment

If an environment selector is provided, use sandbox or test mode while setting up and validating the integration. Do not accidentally enter live credentials into a test setup or vice versa.

6

Save and review

Save the settings, then carefully review the provider selection and any masked credential fields. A saved configuration should not be treated as a confirmed successful connection unless the interface or an actual test clearly verifies it.

7

Run a provider-approved test

Use the provider's sandbox/test tools and a documented Shilte test flow, where available. Confirm that the transaction outcome is handled correctly by both the provider and the connected Shilte workflow before enabling live payments.

5. Testing and payment readiness

Testing is a crucial step. A payment integration can appear configured while a transaction still fails because of credentials, account restrictions, backend connection issues, callback handling, or unsupported payment methods.

Test checklist

  • Confirm the selected provider and merchant account are correct.
  • Check that test/sandbox credentials are being used in the test environment.
  • Use only provider-approved test payment details or sandbox transactions.
  • Verify the expected success and failure outcomes where test flows are supported.
  • Check whether payment status is correctly reflected in the connected business workflow.
  • Verify notifications, receipts, or order updates only if those features are configured and tested.
  • Review the provider dashboard to reconcile test transactions.
  • Before live launch, confirm production credentials, account approval, and all required provider-side settings.
Ready for live payments? Only move to production after the provider confirms your merchant account is eligible, your configuration is secure, and you have completed a documented end-to-end test of the actual payment flow.

6. Keep payment credentials safe

Payment credentials are sensitive. A secret key, consumer secret, passkey, or private credential can allow access to payment-related services and should be treated as confidential.

Good security practices

  • Never post secrets in public chat, tickets, tutorials, or screenshots.
  • Use credentials issued for the correct business account.
  • Limit access to staff who genuinely need it.
  • Rotate/revoke credentials if they may have been exposed.
  • Use secure server-side storage and handling for secrets.

Important implementation caution

Provider secrets should not be exposed in client-side code, browser storage, public JavaScript, or unsecured database documents. Production integrations should securely handle secrets on the server/backend and follow provider security guidance.

Do not use live credentials in a demonstration or tutorial. If you need to share a screenshot for support, mask the key and any merchant-sensitive values before sending it.

7. How payments fit into business workflows

Payment configuration is only one part of the customer journey. A complete payment experience may involve a product or service selection, checkout, provider processing, payment confirmation, order or booking updates, and customer support. Which steps are automated depends on the connected Shilte features and the integration that is actually active.

Customer checkout

A customer selects a product or service and follows the payment steps presented by the configured flow.

Payment status

Payment status should be verified through the provider's supported confirmation mechanism—not inferred from a screenshot or customer claim alone.

Business operations

When connected and implemented, payment status can inform order handling, customer updates, or staff follow-up.

Support and reconciliation

Use provider records to investigate disputes, pending transactions, reversals, and mismatched payment or order records.

For a business using Shilte AI chat or website automation, payment-related conversations should be designed carefully. The AI can provide guidance or direct customers through the available flow, but it should not claim that a payment is completed unless a trusted system confirms that status.

8. Troubleshooting common issues

Credentials are rejected

Re-check for missing characters, accidental spaces, wrong key type, wrong merchant account, and environment mismatch. If the key is expired or revoked, generate or request a replacement through the provider.

Payment option is selected but checkout does not work

Provider selection and credential saving alone may not complete a live checkout integration. Confirm the actual checkout flow is implemented, enabled, and tested for your business and provider.

Test transaction does not appear

Confirm the correct test account and environment, allow for provider processing delays, and compare the transaction with your provider dashboard or test logs.

Payment appears successful at the provider, but Shilte does not update

Check the confirmation/callback or webhook handling, relevant backend logs, transaction identifiers, and order or booking logic. Do not manually mark the transaction paid without validating the provider record.

Not sure which provider to choose?

Compare the provider's supported country, payment methods, merchant requirements, fees, settlement timing, customer experience, and your business's needs. Start with a provider you can properly onboard and test.

9. Frequently asked questions

Does saving my payment settings mean I can accept payments immediately?

No. Saving settings only records configuration. Provider approval, secure credential handling, the operational integration, and successful testing are required before relying on payment processing.

Can I use multiple payment providers?

The settings interface may show multiple providers, but do not assume simultaneous use or automatic routing is supported. Check the capabilities of your workspace and the current implementation.

Should I use test or live credentials?

Use test credentials in the sandbox/test environment while validating the integration. Switch to live credentials only when you are approved and ready for real transactions, following provider and Shilte guidance.

Where do I obtain my credentials?

Get them from your own payment provider's official dashboard or developer portal. Shilte does not issue your merchant API credentials.

What should I do if I suspect a secret has leaked?

Revoke or rotate the exposed credential promptly in your provider dashboard, review relevant activity, and update the secure configuration with the replacement. Never repost the exposed secret.

Will Shilte automatically mark an order as paid?

Only when the relevant payment-confirmation logic is integrated and operating correctly. A chatbot or customer message is not proof of payment; confirm payment through a trusted provider/system record.

10. Video walkthrough

Use this section for a recorded walkthrough of the payment configuration screen, demonstrating how to select a provider, what fields are displayed, and how to review configuration without exposing any sensitive information.

Continue learning

Once you understand payment configuration, explore other Shilte tutorials to connect payments with customer conversations, commerce management, leads, and your wider business workflow.