Complete walkthrough of the payment flow lifecycle with type-safe responses using the nekuda SDK.
Initialize Client
NekudaClient
with your API key.Create User Context
UserContext
by providing a unique user_id
for your end-user.Create Mandate
MandateData
object. This action
returns a mandate_id
.Request Reveal Token
mandate_id
to get a short-lived, single-use token to access card
details.Reveal Card Details
user_id
is required to create a user context.
A MandateData
object must be created and submitted to the API via
user.create_mandate()
to obtain a mandate_id
. This mandate_id
is then
required to request a reveal_token
.MandateCreateResponse
CardRevealTokenResponse
CardDetailsResponse
https://api.nekuda.ai
.
Automatic Response Validation
reveal_token
) are single-use and time-limited. Store them
securely if necessary, but ideally, use them immediately after generation.max_retries
. For very high-volume applications, monitor API usage and consider if additional client-side rate limiting logic is beneficial.