search

VivaPayments / API

Index of Viva Wallet open source projects on GitHub.
139 stars 163 forks source link

How to get the Custom identification code assigned to the device #2447

Open pradelet opened 11 months ago

pradelet commented 11 months ago

Hello

When i try to detect the terminal i need to send the Custom identification code assigned to the device by the merchant

Where can i found this information

Thanks

VivaWalletCustomerSupport commented 11 months ago

Hello @pradelet,

Thank you for your message. Kindly note that the Custom identification code, is the sourceCode parameter. A 4-digit code generated after creating a new payment source. To add a new payment source for stores, please follow the steps below: https://developer.vivawallet.com/getting-started/create-a-payment-source/payment-source-for-stores/

Terminals can be linked to ‘Stores’. Additional information in the link below: https://developer.vivawallet.com/tutorials/pos-terminals/activate-pos-devices/

Kind regards, Viva Wallet E-commerce Support Team

pradelet commented 11 months ago

Hello I have a problem with the 'Search Pos Device'

My first request is OK

POST /connect/token HTTP/1.1 Connection: Keep-Alive Content-Type: application/x-www-form-urlencoded Accept: application/json, text/plain; q=0.9, text/html;q=0.8, Accept-Charset: utf-8, *;q=0.8 Authorization: Basic bXUzMWcxcHd1aGtxdzEzNGpvcDY4M3NrbjM1M292MXc5ZnJscHo0MDMwbWYyLmFwcHMudml2YXBheW1lbnRzLmNvbTphQzk2TjE5d21rNkw1UHdMM3VoU2gxNFQyRThlM1Y= User-Agent: Embarcadero RESTClient/1.0 Content-Length: 29 Host: accounts.vivapayments.com

Response access_token=eyJhbGciOiJSUzI1NiIsImtpZCI6IjYyODk4N0E3MDQ2QTUyQzkzMDY2NDJFMkJGQjBBNUY5OUJFQkFCQkVSUzI1NiIsIng1dCI6IllvbUhwd1JxVXNrd1prTGl2N0NsLVp2cnE3NCIsInR5cCI6ImF0K2p3dCJ9.eyJpc3MiOiJodHRwczovL2FjY291bnRzLnZpdmFwYXltZW50cy5jb20iLCJuYmYiOjE2OTU3OTk3MzMsImlhdCI6MTY5NTc5OTczMywiZXhwIjoxNjk1ODAzMzMzLCJhdWQiOlsiY29yZV9hcGkiLCJlY3JfYXBpIiwiaHR0cHM6Ly9hY2NvdW50cy52aXZhcGF5bWVudHMuY29tL3Jlc291cmNlcyJdLCJzY29wZSI6WyJ1cm46dml2YTpwYXltZW50czpjb3JlOmFwaTpwb3NtYW5hZ2VtZW50IiwidXJuOnZpdmE6cGF5bWVudHM6Y29yZTphcGk6cG9zbWFuYWdlbWVudDp1c2VyY29kZXM6dmVyaWZ5IiwidXJuOnZpdmE6cGF5bWVudHM6ZWNyOmFwaSJdLCJjbGllbnRfaWQiOiJtdTMxZzFwd3Voa3F3MTM0am9wNjgzc2tuMzUzb3YxdzlmcmxwejQwMzBtZjIuYXBwcy52aXZhcGF5bWVudHMuY29tIiwidXJuOnZpdmE6cGF5bWVudHM6Y2xpZW50X3BlcnNvbl9pZCI6IkI3QUIxREFELTM3NDctRUUxMS1CRTZELTAwMEQzQUIwQjQ4NyJ9.svNvR-Q5A02H74O7Y-CRZISJU2Is25IOsMc2jCqh5HD0xDty0STGDT42102BJPmTqq6JW-TGHR_MuENLsqwaakdHD0VFntIyKgHp2bTYKfwEvKbDzS9g9G2DCJUqgw9ctZtYh7v-ZtIFo4o9dYaVCtx1t-64t8_R3OzCXPLaYQQJK5kovRa0Xuotfspr-mR00u_PQGZEicJHp4HvdgLfVkb75PoIt1mYXJEuuM59SDK07SBrqgo6Z-YeMUZFLN6C8oL1vrlIdES0TtfJcXlUUW7yqcPI_HXVnhUfjKLT1L-7SEszfEyP5Ck4kJxn1uj3EonTR5DCBh2han7-nyHW-_z75EqDo-1mQrE5mUOUf_HhP1C1PY1HrS9RhZFnXdr0Z0zEqlKSXs_sUrkRq7j1zVNRY6RwTKK8HaJt89fck3a5XpBAByC8C0E93AC08o_z779kWMUtf5tnDwV03ugBAJTPfL1remz-y5mVtWnHoyE5QwR7TRKsLF2Jl_fxVnud3CYtraGNuu6bN9mWDOOPAsM_lgiyy929qY_p9aH9NHmZez_Kkr5bZ8CVbCaT_PwnLoN732jWLS1HoYhyxp07NFyXCl0MoAGRAzB0NLNMWN9kdAO-HXm7Ae-91TP1C-KqD5cE0AP2M9p4zvNDy3MxLnhLihkogJLuyggSSffvRME

expires_in=3600 scope=urn:viva:payments:core:api:posmanagement urn:viva:payments:core:api:posmanagement:usercodes:verify urn:viva:payments:ecr:api token_type=Bearer

But for the request 'Search Pos Device' i have an error

Error : HTTP/1.1 401 Unauthorized {"detail":"Could not validate credentials"}

The request is

POST /ecr/v1/devices:search HTTP/1.1 Connection: Keep-Alive Content-Type: application/json Accept: application/json Accept-Charset: utf-8, *;q=0.8 Authorization: Bearer "eyJhbGciOiJSUzI1NiIsImtpZCI6IjYyODk4N0E3MDQ2QTUyQzkzMDY2NDJFMkJGQjBBNUY5OUJFQkFCQkVSUzI1NiIsIng1dCI6IllvbUhwd1JxVXNrd1prTGl2N0NsLVp2cnE3NCIsInR5cCI6ImF0K2p3dCJ9.eyJpc3MiOiJodHRwczovL2FjY291bnRzLnZpdmFwYXltZW50cy5jb20iLCJuYmYiOjE2OTU3OTk3MzMsImlhdCI6MTY5NTc5OTczMywiZXhwIjoxNjk1ODAzMzMzLCJhdWQiOlsiY29yZV9hcGkiLCJlY3JfYXBpIiwiaHR0cHM6Ly9hY2NvdW50cy52aXZhcGF5bWVudHMuY29tL3Jlc291cmNlcyJdLCJzY29wZSI6WyJ1cm46dml2YTpwYXltZW50czpjb3JlOmFwaTpwb3NtYW5hZ2VtZW50IiwidXJuOnZpdmE6cGF5bWVudHM6Y29yZTphcGk6cG9zbWFuYWdlbWVudDp1c2VyY29kZXM6dmVyaWZ5IiwidXJuOnZpdmE6cGF5bWVudHM6ZWNyOmFwaSJdLCJjbGllbnRfaWQiOiJtdTMxZzFwd3Voa3F3MTM0am9wNjgzc2tuMzUzb3YxdzlmcmxwejQwMzBtZjIuYXBwcy52aXZhcGF5bWVudHMuY29tIiwidXJuOnZpdmE6cGF5bWVudHM6Y2xpZW50X3BlcnNvbl9pZCI6IkI3QUIxREFELTM3NDctRUUxMS1CRTZELTAwMEQzQUIwQjQ4NyJ9.svNvR-Q5A02H74O7Y-CRZISJU2Is25IOsMc2jCqh5HD0xDty0STGDT42102BJPmTqq6JW-TGHR_MuENLsqwaakdHD0VFntIyKgHp2bTYKfwEvKbDzS9g9G2DCJUqgw9ctZtYh7v-ZtIFo4o9dYaVCtx1t-64t8_R3OzCXPLaYQQJK5kovRa0Xuotfspr-mR00u_PQGZEicJHp4HvdgLfVkb75PoIt1mYXJEuuM59SDK07SBrqgo6Z-YeMUZFLN6C8oL1vrlIdES0TtfJcXlUUW7yqcPI_HXVnhUfjKLT1L-7SEszfEyP5Ck4kJxn1uj3EonTR5DCBh2han7-nyHW-_z75EqDo-1mQrE5mUOUf_HhP1C1PY1HrS9RhZFnXdr0Z0zEqlKSXs_sUrkRq7j1zVNRY6RwTKK8HaJt89fck3a5XpBAByC8C0E93AC08o_z779kWMUtf5tnDwV03ugBAJTPfL1remz-y5mVtWnHoyE5QwR7TRKsLF2Jl_fxVnud3CYtraGNuu6bN9mWDOOPAsM_lgiyy929qY_p9aH9NHmZez_Kkr5bZ8CVbCaT_PwnLoN732jWLS1HoYhyxp07NFyXCl0MoAGRAzB0NLNMWN9kdAO-HXm7Ae-91TP1C-KqD5cE0AP2M9p4zvNDy3MxLnhLihkogJLuyggSSffvRME" User-Agent: Embarcadero RESTClient/1.0 Content-Length: 36 Host: api.vivapayments.com

Base url : BaseURL := 'https://api.vivapayments.com/ecr/v1/devices:search'; Scope := 'urn:viva:payments:ecr:api';

Body : {"statusId":"1","sourceCode":"6904"}

Maybe somethings is missing ?

Thanks

Radelet pascal Manager

@.***

DELTALOG SPRL

Rue Drève du bois 1a - 1325 Chaumont-Gistoux TVA BE0460.334.086 Belfius : BE88 0688 9601 9541

------ Message d'origine ------ De "VivaWalletCustomerSupport" @.**@.>> À "VivaPayments/API" @.**@.>> Cc "Pascal Radelet" @.**@.>>; "Mention" @.**@.>> Date 26-09-23 16:13:04 Objet Re: [VivaPayments/API] How to get the Custom identification code assigned to the device (Issue #2447)

Hello @pradelethttps://github.com/pradelet,

Thank you for your message. Kindly note that the Custom identification code, is the sourceCode parameter. A 4-digit code generated after creating a new payment source. To add a new payment source for stores, please follow the steps below: https://developer.vivawallet.com/getting-started/create-a-payment-source/payment-source-for-stores/

Terminals can be linked to ‘Stores’. Additional information in the link below: https://developer.vivawallet.com/tutorials/pos-terminals/activate-pos-devices/

Kind regards, Viva Wallet E-commerce Support Team

— Reply to this email directly, view it on GitHubhttps://github.com/VivaPayments/API/issues/2447#issuecomment-1735627891, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL32VVXK3WXBO2NEH5BDUF3X4LPHBANCNFSM6AAAAAA5HYZLFU. You are receiving this because you were mentioned.Message ID: @.***>

VivaWalletCustomerSupport commented 11 months ago

Hello @pradelet,

Thank you for your swift response. Please note that the POS API credentials must be used for the Cloud REST (EFT POS) API.

Kind regards, Viva Wallet E-commerce Support Team

pradelet commented 11 months ago

Hello That's what i done;

vusername := 'mu31g1pwuhkqw134jop683skn353ov1w9frlpz4030mf2.apps.vivapayments.com'; vPassword := 'aC96N19wmk6L5PwL3uhSh14T2E8e3V';

  if RESTResponse.StatusCode = 200 then
    begin
      if Assigned(JSONResponse.GetValue('access_token')) then  oAuth2.accesstoken := JSONResponse.GetValue('access_token').ToString;
      if Assigned(JSONResponse.GetValue('expires_in'))   then  expire := JSONResponse.GetValue('expires_in').ToString;
      if Assigned(JSONResponse.GetValue('token_type'))   then  token_type := JSONResponse.GetValue('token_type').Tostring;
      if Assigned(JSONResponse.GetValue('scope'))        then  oAuth2.Scope := JSONResponse.GetValue('scope').ToString;

oAuth2.Scope := 'urn:viva:payments:ecr:api';
OAuth2.ClientID     := vUsername;
oAuth2.ClientSecret := vPassword;
OAUth2.AccessTokenExpiry := incsecond(now,3600);

Radelet pascal Manager

@.***

DELTALOG SPRL

Rue Drève du bois 1a - 1325 Chaumont-Gistoux TVA BE0460.334.086 Belfius : BE88 0688 9601 9541

------ Message d'origine ------ De "VivaWalletCustomerSupport" @.**@.>> À "VivaPayments/API" @.**@.>> Cc "Pascal Radelet" @.**@.>>; "Mention" @.**@.>> Date 27-09-23 10:48:54 Objet Re: [VivaPayments/API] How to get the Custom identification code assigned to the device (Issue #2447)

Hello @pradelethttps://github.com/pradelet,

Thank you for your swift response. Please note that the POS API credentialshttps://developer.vivawallet.com/getting-started/find-your-account-credentials/pos-apis-credentials/ must be used for the Cloud REST (EFT POS) API.

Kind regards, Viva Wallet E-commerce Support Team

— Reply to this email directly, view it on GitHubhttps://github.com/VivaPayments/API/issues/2447#issuecomment-1736976743, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL32VVVTH37JLAMKZF5PPT3X4PR7NANCNFSM6AAAAAA5HYZLFU. You are receiving this because you were mentioned.Message ID: @.***>

pradelet commented 11 months ago

Hello

This is the parameters to give to my component

The parameters to configure in the TOAuth2Authenticator component in Delphi depend on the specific OAuth 2.0 flow and authentication provider you are working with. However, there are common parameters that you typically need to set when configuring an OAuth 2.0 authenticator in Delphi:

  1. AuthEndpoint: The URL of the OAuth 2.0 authorization endpoint. This is typically the URL where the user is redirected to log in and grant consent.

  2. TokenEndpoint: The URL of the OAuth 2.0 token endpoint. This is the URL used to exchange the authorization code for an access token.

  3. RedirectURL: The redirection URL that you registered with the OAuth 2.0 provider. This is the URL to which the user is redirected after a successful authentication.

  4. ClientId: The client identifier (Client ID) you obtained when you registered your application with the OAuth 2.0 provider.

  5. ClientSecret: The client secret (Client Secret) you obtained when registering your application. Keep this secret confidential.

  6. ResponseType: The expected response type from the OAuth 2.0 provider. This depends on the OAuth 2.0 flow you are using, such as "code" for the authorization code flow or "token" for the implicit authorization flow.

  7. Scope: The permissions you are requesting from the user. This depends on the specific functionalities you want to access.

  8. AccessToken: The OAuth 2.0 access token after successful authentication. This can also be used to add a previously obtained token if necessary.

  9. TokenType: The type of access token being used. It is typically "Bearer" for most cases.

Thas is what i DO vusername := 'mu31g1pwuhkqw134jop683skn353ov1w9frlpz4030mf2.apps.vivapayments.com'; vPassword := 'aC96N19wmk6L5PwL3uhSh14T2E8e3V';

RESTClient1.BaseURL := 'https://accounts.vivapayments.com/connect/token';
RESTClient1.SecureProtocols := [THTTPSecureProtocol.TLS1, THTTPSecureProtocol.TLS11, THTTPSecureProtocol.TLS12];
RESTClient1.Authenticator := HTTPBasicAuthenticator1;
RESTRequest1.Method := TRESTRequestMethod.rmPost;
RESTClient1.AddParameter('grant_type','client_credentials');
HTTPBasicAuthenticator1.Username := vusername;
HTTPBasicAuthenticator1.Password := vpassword;
RESTResponse := TRESTResponse.Create(nil);
RESTRequest1.Response := RESTResponse;

try
  RESTRequest1.Execute;
  if Assigned(RESTResponse.JSONValue) then
  begin
    jValue := RESTResponse.JSONValue;

    // Parsear el JSON
    JSONResponse := TJSONObject.Create;
    JSONResponse := RESTResponse.JSONValue as TJSONObject;
    if RESTResponse.StatusCode = 200 then
    begin
      if Assigned(JSONResponse.GetValue('access_token')) then  oAuth2.accesstoken := JSONResponse.GetValue('access_token').ToString;
      if Assigned(JSONResponse.GetValue('expires_in'))   then  expire := JSONResponse.GetValue('expires_in').ToString;
      if Assigned(JSONResponse.GetValue('token_type'))   then  token_type := JSONResponse.GetValue('token_type').Tostring;
      if Assigned(JSONResponse.GetValue('scope'))        then  oAuth2.Scope := JSONResponse.GetValue('scope').ToString;
    end
    else
    begin
      if Assigned(JSONResponse.GetValue('error')) then   error := 'Error: ' + JSONResponse.GetValue('error').ToString;
    end;
    RESTResponse.Free;
  end;
except on E:Exception do
  begin
    error := 'Error: ' + RESTResponse.ErrorMessage + ' Error: ' + E.Message;
  end;
end;

// TO HERE EVERYTHING IS OK

T_RESTClient.BaseURL := 'https://api.vivapayments.com/ecr/v1/devices:search'; T_RESTClient.SecureProtocols := [THTTPSecureProtocol.TLS1, THTTPSecureProtocol.TLS11, THTTPSecureProtocol.TLS12]; T_RESTClient.AddParameter('grant_type','client_credentials');

oAuth2.Scope := 'urn:viva:payments:ecr:api';
OAuth2.ClientID     := vUsername;
oAuth2.ClientSecret := vPassword;
OAUth2.AccessTokenExpiry := incsecond(now,3600);
oAuth2.AccessTokenEndpoint :=  'https://accounts.vivapayments.com/connect/token';
oauth2.AuthorizationEndpoint := 'https://accounts.vivapayments.com/connect/token';
oauth2.RedirectionEndpoint   := 'https://api.vivapayments.com/ecr/v1/devices:search';

T_RESTRequest.Method := TRESTRequestMethod.rmPost;
T_restrequest.AddParameter('Content-Type','application/json', pkHTTPHEADER, [poDoNotEncode]);
RESTResponse := TRESTResponse.Create(nil);
T_RESTRequest.Response := RESTResponse;

Radelet pascal Manager

@.***

DELTALOG SPRL

Rue Drève du bois 1a - 1325 Chaumont-Gistoux TVA BE0460.334.086 Belfius : BE88 0688 9601 9541

------ Message d'origine ------ De "VivaWalletCustomerSupport" @.**@.>> À "VivaPayments/API" @.**@.>> Cc "Pascal Radelet" @.**@.>>; "Mention" @.**@.>> Date 27-09-23 10:48:54 Objet Re: [VivaPayments/API] How to get the Custom identification code assigned to the device (Issue #2447)

Hello @pradelethttps://github.com/pradelet,

Thank you for your swift response. Please note that the POS API credentialshttps://developer.vivawallet.com/getting-started/find-your-account-credentials/pos-apis-credentials/ must be used for the Cloud REST (EFT POS) API.

Kind regards, Viva Wallet E-commerce Support Team

— Reply to this email directly, view it on GitHubhttps://github.com/VivaPayments/API/issues/2447#issuecomment-1736976743, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL32VVVTH37JLAMKZF5PPT3X4PR7NANCNFSM6AAAAAA5HYZLFU. You are receiving this because you were mentioned.Message ID: @.***>

VivaWalletCustomerSupport commented 11 months ago

Hello @pradelet,

Thank you for your reply. As we observed in the beginning and in the end of your access token you are using quotation marks ("). Can you please remove them and try again?

Kind regards, Viva Wallet E-commerce Support Team

pradelet commented 11 months ago

Great that's it

Radelet pascal Manager

@.***

DELTALOG SPRL

Rue Drève du bois 1a - 1325 Chaumont-Gistoux TVA BE0460.334.086 Belfius : BE88 0688 9601 9541

------ Message d'origine ------ De "VivaWalletCustomerSupport" @.**@.>> À "VivaPayments/API" @.**@.>> Cc "Pascal Radelet" @.**@.>>; "Mention" @.**@.>> Date 27-09-23 14:23:23 Objet Re: [VivaPayments/API] How to get the Custom identification code assigned to the device (Issue #2447)

Hello @pradelethttps://github.com/pradelet,

Thank you for your reply. As we observed in the beginning and in the end of your access token you are using quotation marks ("). Can you please remove them and try again?

Kind regards, Viva Wallet E-commerce Support Team

— Reply to this email directly, view it on GitHubhttps://github.com/VivaPayments/API/issues/2447#issuecomment-1737286067, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL32VVXQAVA5ROQJEWXYWADX4QLDXANCNFSM6AAAAAA5HYZLFU. You are receiving this because you were mentioned.Message ID: @.***>

pradelet commented 11 months ago

Hello

Just one other question

Initiate a Sales Request

[Run in Postman]https://app.getpostman.com/run-collection/18763635-9ef00dd4-fd33-4dc0-93ee-5e2d0a8b4f2d?action=collection%2Ffork&collection-url=entityId%3D18763635-9ef00dd4-fd33-4dc0-93ee-5e2d0a8b4f2d%26entityType%3Dcollection%26workspaceId%3D71008394-7296-44d9-ad1c-ae1f239b5574

Use this API Call to initiate a sale transaction to the EFT POS device.

Please note: for this call, please generate a Bearer Tokenhttps://developer.vivawallet.com/apis-for-point-of-sale/card-terminals-devices/rest-api/eft-pos-api-documentation/#tag/Bearer-Token with your POS APIs credentialshttps://developer.vivawallet.com/getting-started/find-your-account-credentials/pos-apis-credentials/#find-your-pos-apis-credentials.

AUTHORIZATIONS: OAuth2https://developer.vivawallet.com/apis-for-point-of-sale/card-terminals-devices/rest-api/eft-pos-api-documentation/#section/Authentication/OAuth2 (urn:viva:payments:ecr:api) REQUEST BODY SCHEMA: application/json sessionId required

string

Transaction session identification

terminalId required

string

Terminal identification - the serial number of the terminal

cashRegisterId required

string

Cash register identification - set by the merchant

What is the cashregisterId, where can i found It

Thanks

Radelet pascal Manager

@.***

DELTALOG SPRL

Rue Drève du bois 1a - 1325 Chaumont-Gistoux TVA BE0460.334.086 Belfius : BE88 0688 9601 9541

------ Message d'origine ------ De "VivaWalletCustomerSupport" @.**@.>> À "VivaPayments/API" @.**@.>> Cc "Pascal Radelet" @.**@.>>; "Mention" @.**@.>> Date 27-09-23 14:23:23 Objet Re: [VivaPayments/API] How to get the Custom identification code assigned to the device (Issue #2447)

Hello @pradelethttps://github.com/pradelet,

Thank you for your reply. As we observed in the beginning and in the end of your access token you are using quotation marks ("). Can you please remove them and try again?

Kind regards, Viva Wallet E-commerce Support Team

— Reply to this email directly, view it on GitHubhttps://github.com/VivaPayments/API/issues/2447#issuecomment-1737286067, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL32VVXQAVA5ROQJEWXYWADX4QLDXANCNFSM6AAAAAA5HYZLFU. You are receiving this because you were mentioned.Message ID: @.***>

VivaWalletCustomerSupport commented 11 months ago

Hello @pradelet,

Thank you for the swift response. Kindly note that the cashregisterId, is an id which you set in your cash register.

Kind regards, Viva Wallet E-commerce Support Team

VivaWalletCustomerSupport commented 11 months ago

Hello @pradelet,

We just wanted to follow up on the reply we sent yesterday. We were simply wondering if you read our response.

In any case this ticket will remain active for at least 24 hours, so that you can come back if you wish.

However, if you have any questions, please don't hesitate to reply here and we'd be happy to help!

Kind regards, Viva Wallet E-commerce Support Team

pradelet commented 11 months ago

Hello Everything seems to be working fine now. I find that the delay between sending the "SALES" request and the terminal's reaction is quite long, between 10 and 15 seconds.

Is this normal

THANKS

Radelet pascal Manager

@.***

DELTALOG SPRL

Rue Drève du bois 1a - 1325 Chaumont-Gistoux TVA BE0460.334.086 Belfius : BE88 0688 9601 9541

------ Message d'origine ------ De "VivaWalletCustomerSupport" @.**@.>> À "VivaPayments/API" @.**@.>> Cc "Pascal Radelet" @.**@.>>; "Mention" @.**@.>> Date 28-09-23 16:15:11 Objet Re: [VivaPayments/API] How to get the Custom identification code assigned to the device (Issue #2447)

Hello @pradelethttps://github.com/pradelet,

We just wanted to follow up on the reply we sent yesterday. We were simply wondering if you read our response.

In any case this ticket will remain active for at least 24 hours, so that you can come back if you wish.

However, if you have any questions, please don't hesitate to reply here and we'd be happy to help!

Kind regards, Viva Wallet E-commerce Support Team

— Reply to this email directly, view it on GitHubhttps://github.com/VivaPayments/API/issues/2447#issuecomment-1739321892, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL32VVWXOPCMEEBPOYR4T5DX4WA67ANCNFSM6AAAAAA5HYZLFU. You are receiving this because you were mentioned.Message ID: @.***>

VivaWalletCustomerSupport commented 11 months ago

Hello @pradelet,

Thank you for the update. Can you send us a short video showing the process followed and the delay you mentioned?

You can send it to the following e-mail: support@vivawallet.com Please add the GitHub ticket number on the subject of the e-mail.

Kind regards, Viva Wallet E-commerce Support Team

pradelet commented 11 months ago

I have send the video with wetransfer

Thanks

Radelet pascal Manager

@.***

DELTALOG SPRL

Rue Drève du bois 1a - 1325 Chaumont-Gistoux TVA BE0460.334.086 Belfius : BE88 0688 9601 9541

------ Message d'origine ------ De "VivaWalletCustomerSupport" @.**@.>> À "VivaPayments/API" @.**@.>> Cc "Pascal Radelet" @.**@.>>; "Mention" @.**@.>> Date 29-09-23 09:42:17 Objet Re: [VivaPayments/API] How to get the Custom identification code assigned to the device (Issue #2447)

Hello @pradelethttps://github.com/pradelet,

Thank you for the update. Can you send us a short video showing the process followed and the delay you mentioned?

You can send it to the following e-mail: @.**@.> Please add the GitHub ticket number on the subject of the e-mail.

Kind regards, Viva Wallet E-commerce Support Team

— Reply to this email directly, view it on GitHubhttps://github.com/VivaPayments/API/issues/2447#issuecomment-1740453212, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL32VVTAFBJEDDLEDN4N2FDX4Z3VTANCNFSM6AAAAAA5HYZLFU. You are receiving this because you were mentioned.Message ID: @.***>

VivaWalletCustomerSupport commented 11 months ago

Hello @pradelet,

Thank you for the video. Can you please send logs from the terminal menu? Go to More - Send Logs. Also, have you encountered any timeout issues on your server?

Kind regards, Viva Wallet E-commerce Support Team

pradelet commented 11 months ago

Hello

This is send. no timeout on the server

Radelet pascal Manager

@.***

DELTALOG SPRL

Rue Drève du bois 1a - 1325 Chaumont-Gistoux TVA BE0460.334.086 Belfius : BE88 0688 9601 9541

------ Message d'origine ------ De "VivaWalletCustomerSupport" @.**@.>> À "VivaPayments/API" @.**@.>> Cc "Pascal Radelet" @.**@.>>; "Mention" @.**@.>> Date 29-09-23 13:43:05 Objet Re: [VivaPayments/API] How to get the Custom identification code assigned to the device (Issue #2447)

Hello @pradelethttps://github.com/pradelet,

Thank you for the video. Can you please send logs from the terminal menu? Go to More - Send Logs. Also, have you encountered any timeout issues on your server?

Kind regards, Viva Wallet E-commerce Support Team

— Reply to this email directly, view it on GitHubhttps://github.com/VivaPayments/API/issues/2447#issuecomment-1740755401, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL32VVQGB6QVRM7CG4HPBQDX42X4TANCNFSM6AAAAAA5HYZLFU. You are receiving this because you were mentioned.Message ID: @.***>

VivaWalletCustomerSupport commented 11 months ago

Hello @pradelet,

Thank you for the additional information. We will investigate your query further and let you know as soon as we have any updates.

Kind regards, Viva Wallet E-commerce Support Team

pradelet commented 10 months ago

Hello

Do you have a solution for me

Thanks

Radelet pascal Manager

@.***

DELTALOG SPRL

Rue Drève du bois 1a - 1325 Chaumont-Gistoux TVA BE0460.334.086 Belfius : BE88 0688 9601 9541

------ Message d'origine ------ De "VivaWalletCustomerSupport" @.**@.>> À "VivaPayments/API" @.**@.>> Cc "Pascal Radelet" @.**@.>>; "Mention" @.**@.>> Date 29-09-23 14:59:14 Objet Re: [VivaPayments/API] How to get the Custom identification code assigned to the device (Issue #2447)

Hello @pradelethttps://github.com/pradelet,

Thank you for the additional information. We will investigate your query further and let you know as soon as we have any updates.

Kind regards, Viva Wallet E-commerce Support Team

— Reply to this email directly, view it on GitHubhttps://github.com/VivaPayments/API/issues/2447#issuecomment-1740858780, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL32VVXWCHFJYKGKDEH6NADX43A2FANCNFSM6AAAAAA5HYZLFU. You are receiving this because you were mentioned.Message ID: @.***>

VivaWalletCustomerSupport commented 10 months ago

Hello @pradelet,

We would like to inform you that your issue is still under investigation. As soon as our technical checks are over, we will inform you. Thank you for your patience.

Kind regards, Viva Wallet E-commerce Support Team