Skip to main content
Yuno automatically tracks the expiration of every Pix payment based on the configuration in your integration. Before a Pix payment expires, Yuno proactively checks whether it has been completed. If the shopper does not pay in time, Yuno notifies VTEX, which automatically cancels the order.
Saved-card flows and Click to Pay both rely on a customer record being created in Yuno. To enable them, set the Create Customer field to Yes in your Yuno provider configuration. With this option enabled, the plugin creates or updates a Yuno customer record on every payment.
Yes. Orders created with VTEX’s subscriptions feature are supported out of the box. The first purchase is processed like any other card payment. The automatic renewals that follow are charged even though the shopper is not present and no security code (CVV) is entered. Yuno processes them as stored-credential, merchant-initiated (MIT) payments, a classification that lets recurring charges go through instead of being declined.There is nothing extra to configure on the Yuno side: as long as you have set up subscriptions in VTEX, the integration handles them automatically, and your regular checkout is unaffected. Subscriptions apply to card payments only.
The environment is determined by the prefix of your Yuno Public API Key:
  • dev_*, staging_*, and sandbox_* prefixes connect to test environments.
  • prod_* prefixes connect to production.
To switch to production, simply replace your API keys in the VTEX dashboard with your production credentials from the Yuno dashboard.
Use the Soft Descriptor field in your Yuno provider configuration. The text you enter is sent to the acquirer and shown on the shopper’s card statement. We recommend using your store name to help shoppers identify the purchase and reduce chargebacks.
Not necessarily. If your VTEX accounts share the same Yuno credentials (e.g., a franchise model), you can use the Main Account fields in the provider configuration to share catalog and order data. If each account uses its own credentials, you should configure them independently.
Yes. You can connect a single VTEX account to multiple Yuno integrations. Configure Yuno as a provider once for each integration with a distinct Affiliation Name, then select the correct affiliation when activating each payment method.
When a shopper’s cart contains products from different sellers or franchises, VTEX splits the purchase into multiple suborders and charges each one independently. Yuno processes every suborder so the whole order is paid — not just the first part — sharing a single antifraud session across all of them. You can control which antifraud providers receive that shared session with the Antifraud Providers for Split Orders field. See Advanced Scenarios for details.
Yes. VTEX lets you modify an order after it has been placed — useful when the final amount is only known later, such as products sold by weight. If the final total is the same or lower, Yuno captures only the final amount. If it is higher, Yuno charges the difference automatically against the card used on the original order, without the shopper needing to re-enter it.Automatic charges for increased totals apply to credit cards and must be enabled in advance: set Vault Card for Order Modification and Create Customer to Yes in your provider configuration before the orders are placed. See Advanced Scenarios for the full setup.
Open the order in your Yuno dashboard to see the full lifecycle of every payment attempt, including provider responses and errors. Cross-reference the VTEX order ID with the Yuno payment ID to follow the transaction end-to-end.