pwf-transactions

Operations addressed under /pwf-transactions — 2 operations.

check-transaction-approval

POST

https://dg-sandbox.dgpays.com/integration-service

/pwf-transactions/check-approval

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 CheckTransactionApprovalResult.

Field	Declared type	Nullable
`Status`	`PwfTransactionStatus`	no
`ClientIp`	`string`	no
`TimeStamp`	`long?`	yes
`VerificationSignature`	`string`	no
`SecretKey`	`string`	no
`CipherText`	`string`	no
`Content`	`string`	no

Member names are the service's declaration names.

check-transaction-approval › Request Body

transactionToken

string · required

customerId

integer · int32

check-transaction-approval › Responses

Success. An exact, uniquely bound route registration classifies this response as a single-record.

No data returned

start-client-transaction

POST

https://dg-sandbox.dgpays.com/integration-service

/pwf-transactions/start-client

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 StartClientTransactionResponseDto.

Field	Declared type	Nullable
`PushToken`	`string`	no
`TransactionToken`	`string`	no
`VerificationSignature`	`string`	no
`SecretKey`	`string`	no
`CipherText`	`string`	no
`Content`	`string`	no

Member names are the service's declaration names.

start-client-transaction › Request Body

applicationName

string · required

cancelOnBackPress

boolean · required

cancelPendingTransactions

boolean · required

referenceToken

string · required

timeoutDuration

integer · int64 · required

transactionApprovementTypeList

integer[] · required

transactionContent

string · required

transactionName

string · required

object · required

transactionType

integer · int32 · required

start-client-transaction › Responses

Success. An exact, uniquely bound route registration classifies this response as a single-record.

No data returned

POST/pwf-transactions/start-client

curl https://dg-sandbox.dgpays.com/integration-service/pwf-transactions/start-client \
  --request POST \
  --header 'Content-Type: application/json' \
  --data '{
  "applicationName": "",
  "cancelOnBackPress": false,
  "cancelPendingTransactions": false,
  "referenceToken": "",
  "timeoutDuration": 0,
  "transactionApprovementTypeList": [
    0
  ],
  "transactionContent": "",
  "transactionName": "",
  "transactionOwner": {
    "customerId": 0,
    "ownerKey": ""
  },
  "transactionType": 0
}'

Example Request Body

{
  "applicationName": "",
  "cancelOnBackPress": false,
  "cancelPendingTransactions": false,
  "referenceToken": "",
  "timeoutDuration": 0,
  "transactionApprovementTypeList": [
    0
  ],
  "transactionContent": "",
  "transactionName": "",
  "transactionOwner": {
    "customerId": 0,
    "ownerKey": ""
  },
  "transactionType": 0
}

json

The field names and types this operation declares. Replace the values before sending.

application/json

Example Responses

No example specified for this content type

person-infos rm-segments

Integration Service

pwf-transactions

Operations addressed under /pwf-transactions — 2 operations.

check-transaction-approval

POST

https://dg-sandbox.dgpays.com/integration-service

/pwf-transactions/check-approval

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 CheckTransactionApprovalResult.

Field	Declared type	Nullable
`Status`	`PwfTransactionStatus`	no
`ClientIp`	`string`	no
`TimeStamp`	`long?`	yes
`VerificationSignature`	`string`	no
`SecretKey`	`string`	no
`CipherText`	`string`	no
`Content`	`string`	no

Member names are the service's declaration names.

check-transaction-approval › Request Body

transactionToken

string · required

customerId

integer · int32

check-transaction-approval › Responses

Success. An exact, uniquely bound route registration classifies this response as a single-record.

No data returned

start-client-transaction

POST

https://dg-sandbox.dgpays.com/integration-service

/pwf-transactions/start-client

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 StartClientTransactionResponseDto.

Field	Declared type	Nullable
`PushToken`	`string`	no
`TransactionToken`	`string`	no
`VerificationSignature`	`string`	no
`SecretKey`	`string`	no
`CipherText`	`string`	no
`Content`	`string`	no

Member names are the service's declaration names.

start-client-transaction › Request Body

applicationName

string · required

cancelOnBackPress

boolean · required

cancelPendingTransactions

boolean · required

referenceToken

string · required

timeoutDuration

integer · int64 · required

transactionApprovementTypeList

integer[] · required

transactionContent

string · required

transactionName

string · required

object · required

transactionType

integer · int32 · required

start-client-transaction › Responses

Success. An exact, uniquely bound route registration classifies this response as a single-record.

No data returned

POST/pwf-transactions/start-client

curl https://dg-sandbox.dgpays.com/integration-service/pwf-transactions/start-client \
  --request POST \
  --header 'Content-Type: application/json' \
  --data '{
  "applicationName": "",
  "cancelOnBackPress": false,
  "cancelPendingTransactions": false,
  "referenceToken": "",
  "timeoutDuration": 0,
  "transactionApprovementTypeList": [
    0
  ],
  "transactionContent": "",
  "transactionName": "",
  "transactionOwner": {
    "customerId": 0,
    "ownerKey": ""
  },
  "transactionType": 0
}'

Example Request Body

{
  "applicationName": "",
  "cancelOnBackPress": false,
  "cancelPendingTransactions": false,
  "referenceToken": "",
  "timeoutDuration": 0,
  "transactionApprovementTypeList": [
    0
  ],
  "transactionContent": "",
  "transactionName": "",
  "transactionOwner": {
    "customerId": 0,
    "ownerKey": ""
  },
  "transactionType": 0
}

json

The field names and types this operation declares. Replace the values before sending.

application/json

Example Responses

No example specified for this content type

person-infos rm-segments