Skip to main content

Partner Onboarding Journey

Quick Reference

WhatComplete partner onboarding process
WhyUnderstand every phase from first contact to production launch
Reading Time10 min
DifficultyBeginner
PrerequisitesBusiness entity with valid documentation

Onboarding Phases

1

Initial Contact

Reach out to tech.services@a55.tech with:

  • Company name and website
  • Expected monthly transaction volume
  • Target countries and payment methods
  • Integration method preference (H2H, SDK, or Checkout Page)

A55 assigns a dedicated integration engineer to your account within 2 business days.

2

Business Qualification

Submit KYC/KYB documentation:

DocumentRequired For
Certificate of incorporationAll partners
CNPJ registration (Brazil)Brazilian entities
Beneficial ownership declarationAll partners
Processing history (6 months)Volume-based pricing
3

Contract Signing

After qualification, A55 prepares a commercial agreement covering:

  • Processing fees per payment method and country
  • Settlement schedule and currency
  • SLA commitments (uptime, support response time)
  • Chargeback liability terms
4

Technical Onboarding Call

A 60-minute call with your integration engineer covering:

  • API architecture and authentication flow
  • Recommended integration method for your use case
  • Webhook setup and event catalog
  • Sandbox environment walkthrough
  • Timeline and milestone planning
5

Sandbox Credentials Provisioned

You receive:

CredentialPurpose
client_id / client_secretOAuth2 authentication
entity_uuidYour entity identifier
merchant_uuidMerchant configuration
Sandbox Cognito URLToken endpoint
Sandbox API base URLhttps://sandbox.api.a55.tech
6

Integration Development

Build your integration using one of three methods:

MethodBest ForCard Data Handling
Host-to-Host (H2H)Full control, server-sideYou collect, A55 encrypts and vaults
SDK (Drop-in UI)Web/mobile appsA55 SDK captures securely in browser
Checkout PageHosted payment pageA55 manages everything

See the Integration Overview to pick the right method.

7

Integration Testing

Run your integration against sandbox using test cards:

  • Process charges for every payment method you support
  • Test all decline scenarios and error handling paths
  • Verify webhook delivery and signature validation
  • Test refund and cancellation flows
  • Validate 3DS redirect handling (if applicable)
8

Go-Live Review

A55 performs a production readiness review:

  • All test scenarios pass
  • Error handling covers every API response code
  • Webhook signature verification implemented
  • Retry logic with exponential backoff in place
  • Security checklist completed (see Go-Live Checklist)
9

Production Credentials + Monitoring

After approval:

  1. Production client_id / client_secret issued
  2. Production Cognito URL and API base URL provided
  3. Monitoring dashboards configured
  4. Go-live date confirmed and first production charge tested

Post-launch, your integration engineer remains available for 30 days of hypercare support.

Regardless of which integration method you choose, A55 takes care of card data protection:

  • Host-to-Host (H2H): You collect card data and send it to A55 over TLS. A55 encrypts, tokenizes, and vaults it — your servers never need to store card numbers.
  • SDK: Card data goes from the buyer's browser directly to A55. Your servers never see it.
  • Checkout Page: Card data is collected entirely on A55's hosted page at pay.a55.tech. You never touch card data at all.

All three methods benefit from A55's enterprise-grade encryption, tokenization, and secure vault infrastructure.

Timeline

PhaseTypical Duration
Initial contact → Sandbox credentials3–5 business days
Integration development1–4 weeks (varies)
Testing and go-live review2–5 business days
Total2–6 weeks