Mobile BFF Service
string · requiredstring · requiredstring · required
pwf-initate-activation
Operations addressed under /pwf-initate-activation — 1 operation.
mobile-bff-pwf-activation-otp
POST
https://dg-sandbox.dgpays.com/mobile-bff-service
/api/pwf-initate-activation
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Response body, read from the service source
The route declares its response as PwfActivationDto.
| Field | Declared type | Nullable |
|---|---|---|
EncryptedCredentials | string | no |
CustomerId | int | no |
FirstName | string | no |
LastName | string | no |
PhoneNumber | string | no |
Username | string | no |
SmsSuccess | bool | no |
IsTempPassword | bool | no |
CustomerIdGuid | Guid | no |
Success | bool | no |
Member names are the service's declaration names.
Error codes this operation is known to raise
| Code | Status | Meaning |
|---|---|---|
ERR_AURAX_43 | 400 | PHONE_NUMBER_NOT_FOUND |
ERR_AURAX_49 | 400 | USERNAME_NOT_NUMBER |
mobile-bff-pwf-activation-otp › Request Body
applicationNamepassworduserIdentifiermobile-bff-pwf-activation-otp › Responses
Success. An exact, uniquely bound route registration classifies this response as a single-record.
No data returned