A Gruv payment link opens a tokenized guest-checkout page. The page prepares a hosted payment session for the invoice and can forward the payer directly to the provider. The exact payment method and provider experience come from the session created for that link.
What your client sees
- A Guest checkout badge and a Continue to payment heading.
- The invoice reference connected to the link.
- The account ID associated with the checkout descriptor.
- The amount due, including its currency formatting.
- The payment provider named for the current hosted session.
How the hosted session opens
- The payer opens the unique payment-link token.
- Gruv fetches the checkout details. If no actionable hosted session exists yet, the page asks the checkout service to create one.
- An Airwallex-hosted session opens through its hosted checkout path; another configured provider can open through the returned session URL.
- If automatic forwarding does not start, the payer can choose Continue to secure checkout or Continue to payment when that action is shown.
If the link does not continue
- Missing token: return to the original message and open the complete payment link.
- Hosted session unavailable: use Reload payment link or Refresh session once.
- If the service still does not return a hosted session, ask the sender for a fresh payment link instead of editing the URL.
- Before paying, compare the displayed invoice reference and amount with the invoice or request you expected.
The guest-checkout page does not establish the final settlement destination, receipt delivery, refund process, or payment methods for every country. Confirm those account-specific details with the sender or the team that configured the checkout. When asking for help, share the invoice reference and visible error, not payment-card details.