Save to Pay – Partner Onboarding Checklist

Phase 1 – Kickoff

  1. Partner technical point(s) of contact identified

  2. Samsung integration point of contact identified

  3. Confirm program/card type – affects which fields are required in POST /notifications – see user.id, device.id, wallet.id in API Reference.

  4. Confirm end-user entry point/s: in-session redirect, SMS link, or both

Phase 2 – What the partner provides to Samsung

  1. Client TLS certificate – signed by the partner’s own CA, S2P can authenticate when calling the partner’s notification endpoint (mutual SSL)

  2. Outbound notification endpoint URL — staging and production (path for POST /notifications is agreed during onboarding)

  3. Any custom headers Samsung should send with each notification (e.g. an auth token/key)

  4. custom.cardArtUrl — card art image URL

  5. custom.cardName — card display name

  6. custom.partnerLogoUrl — partner logo image URL

  7. custom.partnerName — partner display name

  8. Desired welcomeUrl expiration window, if different from the 24h default

Phase 3 – What Samsung provides to partner

  1. partner-id (UUID) — staging and production

  2. Staging base URL: https://s2p-api.stg.mpay.samsung.com/ext/v1

  3. Production base URL: https://s2p-api.mpay.samsung.com/ext/v1

  4. SDK CDN URLs — staging and production (s2p.min.js)

  5. Samsung's server cert/CA info, so the partner can validate inbound mTLS connections from S2P

  6. Integration docs: API references, SDK guide, end-to-end sequence diagram

Phase 4 – Integration work (Partner-side)

  1. Implement POST /registrations call from the partner backend (mTLS configured, partner-id + request-id headers) — never called from the browser (see architecture notes)

  2. Implement GET /registrations/{regId} for refreshing an expired welcomeUrl

  3. Embed the SDK (s2p.min.js) on the partner frontend; wire up showWelcomeModal/showWelcomeModalPromise

  4. Build and host the POST /notifications endpoint (server-side mTLS, validating Samsung's client cert)

  5. Handle WA_READY synchronously — must return card.data.encryptedData before S2P's timeout

  6. Handle WA_PROVISIONED / WA_PROVISION_FAILURE asynchronously, and self-stabilizing — ⚠️ request-id changes on every retry, so dedupe on event.regId + event.type, not on request-id

  7. If using the SMS-link entry point: build the partner endpoint that fetches a fresh welcomeUrl via GET /registrations/{regId} when the link is opened, and the SMS-sending mechanism itself

Phase 5 – Testing (Staging)

  1. Mutual SSL handshake verified in both directions

  2. POST /registrations end-to-end against staging

  3. SDK flow tested on: desktop/tablet (QR path) and mobile phone (deep-link path)

  4. Foldable devices tested in both folded and unfolded states (device-detection edge case)

  5. WA_READY sync response timing/timeout behavior verified

  6. WA_PROVISIONED / WA_PROVISION_FAILURE async handling and retry/dedupe logic verified

  7. Error responses handled gracefully (400/410/415/503/500 — see per-endpoint tables in Inbound APIs)

  8. welcomeUrl expiration and refresh flow tested

  9. Deep-link fallback tested when the Wallet app isn't installed (user lands on "REDIRECTING" dialog)

Phase 6 – Go-Live

  1. Production partner-id issued and production certs exchanged

  2. Production base URLs and SDK CDN URL confirmed in partner code

  3. Joint sign-off on staging test results

  4. Support/escalation contacts shared for post-launch issues