Add Zap payment method to charge UI flow#127
Merged
Merged
Conversation
Introduce the Zap mandate API on the public `Paystack` surface:
`initiateZapMandate(_:)` initiates a mandate and `listenForZapResponse(onChannel:)`
subscribes for status updates (reusing the Pay-with-Transfer Pusher response shape).
- ZapMandateService posts to `bank/digitalbankmandate/{id}/{transactionId}`,
overriding `baseURL` to `https://standard.paystack.co`
- Make `baseURL` an overridable PaystackService requirement (defaults to
api.paystack.co) so services can target a non-default host
- Add `postForm`/`setFormBody` for application/x-www-form-urlencoded bodies
with percent-encoded fields
- Add ZapMandateRequest/ZapMandateResponse and SupportedBank models
- Decode `supported_banks` from the verify-access-code response
Tests: Zap initiate/listen, form-body encoding, and supported-banks decoding.
Introduce Zap as a new payment channel in the PaystackUI charge flow,
built on the Zap digital bank mandate support added to PaystackCore.
- Add the Zap flow following the established Views/Viewmodels/Models/
Repository layout: ZapView, ZapPaymentView, ZapSessionExpiredView,
ZapViewModel, ZapRepository, and the ZapConfig/ZapDetails/ZapState
models, plus a QRCodeImage component.
- Wire Zap into ChargeViewModel: surface it as a SupportedChannel when
the access code advertises a promoted Zap bank (code "00zap"), and
route single-channel Zap transactions straight to the payment screen.
- Extend ChargePaymentType, SupportedChannel, and VerifyAccessCode
(email + supportedBanks) to carry Zap, and render it from ChargeView.
- ZapViewModel initiates the mandate, displays the QR/payment URL,
counts down the 5-minute mandate window to a session-expired state,
and listens on Pusher for the terminal transaction update.
- Add zapLogo/zapSingleLogo image assets.
- Add ZapViewModelTests and MockZapRepository, and extend
ChargeViewModel/ChargeRepository tests for the Zap channel.
…ature/Zap-on-SDK-UI
Peter-John-paystack
requested review from
a team and
michael-paystack
as code owners
zaheer-paystack
approved these changes
Jun 24, 2026
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce Zap as a new payment channel in the PaystackUI charge flow,
built on the Zap digital bank mandate support added to PaystackCore.
Repository layout: ZapView, ZapPaymentView, ZapSessionExpiredView,
ZapViewModel, ZapRepository, and the ZapConfig/ZapDetails/ZapState
models, plus a QRCodeImage component.
the access code advertises a promoted Zap bank (code "00zap"), and
route single-channel Zap transactions straight to the payment screen.
(email + supportedBanks) to carry Zap, and render it from ChargeView.
counts down the 5-minute mandate window to a session-expired state,
and listens on Pusher for the terminal transaction update.
ChargeViewModel/ChargeRepository tests for the Zap channel.