# InfinitePay hosted checkout integration | Upmy portfolio URL: https://upmy.com.br/en/work/infinitepay-ecommerce-integration/ Language: en Hosted checkout · Integration ## InfinitePay hosted checkout integration Payment-link creation, store return and transaction verification in a dedicated module. [Request a quote↗](https://wa.me/5516988724774?text=Hi%20Weliton!%20I'd%20like%20a%20quote%20for%20InfinitePay%20hosted%20checkout%20integration.)[Explore the workflow ↗](#workflow) Code implemented · payment validation pending 5 workflow stages Custom development UPMY / INTEGRATION ↗ 01 Store purchase → 02 InfinitePay checkout → 03 Verified order update WORKFLOW MAP Need something similar? [Request a quote ↗](https://wa.me/5516988724774?text=Hi%20Weliton!%20I'd%20like%20a%20quote%20for%20InfinitePay%20hosted%20checkout%20integration.) 01 / Context ### The challenge An external checkout needs to preserve its connection to the original purchase so the store can recognize the correct payment. This project explores connecting a Botble store to InfinitePay's hosted checkout. The store organizes the purchase and requests a link; the customer completes the payment step on the provider's page. The integration then needs to reconcile the result with the order that created the charge. The module was structured to preserve that relationship as the customer leaves and returns. Its code includes link creation, order references, notification handling and a payment check. The research confirmed a local implementation, but did not establish a completed approved-payment test or a verified public deployment. 02 / Step by step ### How the workflow works - 01 #### Prepare the purchase Products and quantities are represented in cents. Shipping and fees contribute to the total so the requested amount corresponds to the store order. - 02 #### Create the payment link The server sends the order to the checkout service with a reference and return addresses. The API is expected to return the hosted checkout URL. - 03 #### Pay with the provider The customer follows the external link and uses the options available to that account and checkout. This stage is part of the provider's payment experience. - 04 #### Check the transaction A return or webhook triggers a payment query. The implementation uses transaction identifiers to verify the outcome before completing the local order. - 05 #### Update the store When the response indicates payment, the related orders enter the processing flow. A check avoids repeating completion for orders already marked as paid. 03 / Implementation ### The work The implementation prepares order items and amounts, creates an InfinitePay link and checks the transaction before processing the related orders. - Provider-hosted checkout - Items, shipping and totals linked to the order - Payment verification on return #### Hosted checkout with order continuity The integration's main responsibility is to preserve a reliable reference between the store purchase and the external payment. A browser redirect alone does not establish that funds were received, so the implemented flow includes a dedicated confirmation query. Item preparation matters too. The code accounts for products, shipping and fees and provides an alternative that preserves the expected total when the detailed sum differs. That behavior should be reviewed against representative orders during validation. #### From implementation to operation The module's presence demonstrates the technical structure without claiming that every stage has been approved for the payment account. The next phase is to validate credentials, returns, webhooks, repeated notifications and a complete purchase in an appropriate environment. A quoted project can use this foundation to connect an existing store, adjust customer messages and document how pending payments are handled. The commercial scope depends on current API compatibility, account eligibility and the platform version. 04 / Delivery ### Delivery and context Link creation, return handling, webhook handling and payment verification are present in the code. Financial validation still needs to be documented. #### Deployment considerations - Customers pay on a hosted page; this is not an on-site transparent card checkout. - No approved charge or public payment validation was established for this module. - Recurring payments, financial split and automatic refunds are not demonstrated features. ### Frequently asked questions Does payment happen on my website? The purchase starts on your website, while payment uses an InfinitePay-hosted link. The integration connects the result to the store order. Is the module ready for immediate installation? The code exists and can inform a quoted integration project. Delivery requires a compatibility review and payment validation before operation. ### A similar workflow in your business? Tell me which platform you use, how your workflow operates today and what needs to change. Together, we can define the scope, integrations and acceptance checks for your project. [Request a quote↗](https://wa.me/5516988724774?text=Hi%20Weliton!%20I'd%20like%20a%20quote%20for%20InfinitePay%20hosted%20checkout%20integration.)Scope and pricing tailored to your project. ### Related services [Botble CMS development and custom pluginsPlugins, integrations and improvements for Botble stores and applications.↗](https://upmy.com.br/en/services/botble-development/)[Payment gateway and API integrationsConnect checkout, billing and payment events to your business systems.↗](https://upmy.com.br/en/services/payment-integration/)[Back to projects ↗](https://upmy.com.br/en/work/)