The third party application will trigger the registration process in the payment application. GP then performs the following checks:
- whether the user is logged into GP tom
- whether the value „cliendID“ is filled in (optional), the application checks whether the logged-in user matches the clientID
- the current GP usage of whether the transaction can be initiated
The payment application will generate a transaction ID after receiving the request. This transaction ID will be stored locally and returned to the third party application. Your application should save it and use it for the transaction request.
Exception
Transaction registration has one exception - the Inquiry function, which does not require a registration step. In any case, a transaction ID is required for Inquiry.
Request [RegisterEntity]:
All used *JsonStrings entities must be serialized to the string parameter, as shown in the example below. Example:
String registerEntityJsonString = new Gson().toJson(registerEntity)
CARD
ACCOUNT_PAYMENT
Example:
void transactionRegisterV2(String registerEntityJsonString, ITransactionRegisterListener listener) throws RemoteException
Response [RegisterResultV2Entity]:
In response, we will return a Json string that should be deserialized. Example: