Skip to main content

Checkout Page

Quick Reference

WhatHosted payment page
WhyCard data never touches your origin — A55 handles everything
DifficultyBeginner
PrerequisitesAuthentication → Create charge

Create the charge on your server, then redirect the buyer to A55's hosted experience. Card data never touches your domain — A55 manages card capture, encryption, and 3DS end-to-end.


Why hosted checkout

BenefitDetail
Zero card data on your originCard entry handled entirely by A55
Multi-methodCards, PIX, Apple Pay, Google Pay in one flow
Built-in 3DSA55 runs 3DS inside confirmacion.a55.tech
Mobile-optimizedResponsive hosted pages
Fastest launchMinimal frontend work beyond redirect

Flow

  1. Create a charge via API (POST https://core-manager.a55.tech/api/v1/bank/wallet/charge/).
  2. Read charge_payment_url (or equivalent checkout URL) from the response.
  3. Redirect the buyer to https://pay.a55.tech/checkout/v2/{uuid} (use the URL returned by the API when provided).
What the hosted page handles

Card entry, PIX QR display, Apple Pay / Google Pay, and 3DS inside A55-controlled domains.

Your responsibilities: create the charge with correct amount and currency, set redirect_url / return URLs as required, and subscribe to webhooks for final status.


Redirect code

window.location.href = chargePaymentUrl;
Environments

Keep charge UUIDs stable across environments; use sandbox hosts and credentials when testing redirects.

3DS on hosted checkout

Authentication runs inside A55's domain. You do not handle url_3ds manually for standard hosted checkout flows.