SDK Integration (V1)

Deprecated

SDK V1 is deprecated as of January 2025. Migrate to SDK V2 before December 2025. See the migration guide below.

Quick Reference

WhatLegacy A55Pay.pay()

WhyParity for merchants on V1 while planning migration to V2

DifficultyIntermediate

PrerequisitesSDK V2 → Authentication

Legacy

SDK V1 is legacy. It uses older A55Pay.pay(config) and legacy 3DS paths. New integrations should use SDK V2.

The V1 SDK is documented so existing merchants can maintain behavior while planning migration. Behavior and error codes may differ from V2.

---

Primary method: A55Pay.pay(config)

A55Pay.pay

A55Pay.pay({
  chargeUuid: '00000000-0000-4000-8000-000000000001',
  holder: 'Jane Doe',
  number: '4111111111111111',
  month: '12',
  year: '2030',
  cvc: '123',
  onSuccess: (payload) => {},
  onFailed: (err) => {},
});

---

Field names: V1 vs V2

V1	V2 (userData)
holder	name
number	card_number
month / year	card_expiry_month / card_expiry_year
cvc	card_cvv

---

Migration path

1. Map V1 fields to V2 equivalents in a small adapter layer.
2. Switch the entrypoint from pay() to payV2().
3. Update 3DS handling (legacy provider 3DS flows vs A55-hosted 3DS in V2).
4. Test in sandbox: validate webhooks and callbacks end-to-end.
5. Monitor in production; run an A/B cutover if traffic allows.

Adapter first

Map fields once in an adapter module, switch to payV2, then validate 3DS and webhooks before removing V1 code paths.

---

Notes

Behavior

Error payloads, edge cases, and 3DS redirects may not match SDK V2. Legacy 3DS paths are not identical to current A55-hosted 3DS on confirmacion.a55.tech.

SDK V2 →payV2, open, and current 3DS.Checkout Page →Hosted checkout without embedded SDK.Integration overview →Compare H2H, SDK, and Checkout.