Discussions

Hi, I'm at the developer sandbox trying to get createPayment to work. I'm using your page here: https://developer.veem.com/reference/createpaymentusingpost_1 Here's my request: curl --request POST \ --url https://sandbox-api.veem.com/veem/v1.1/payments \ --header 'Accept: application/json' \ --header 'Authorization: Bearer b24dc903-5ea0-4dc1-bfe0-91eaed583d36' \ --header 'Content-Type: application/json' \ --data ' { "amount": { "currency": "USD", "number": 1000 }, "payee": { "businessName": "Shivan Eyecare", "countryCode": "US", "email": "[email protected]", "firstName": "Shivan", "lastName": "Dragon", "type": "Business", "phone": "18193180000" }, "purposeOfPayment": "Vision Claims" } ' Here's the response: { "code": 50000000, "message": "Value is unexpected: 11089", "timestamp": "2021-11-17T22:46:23.570", "fileName": "VeemResponseHandler.java", "lineNumber": 89 } The value "11089" is the customer ID for "Shivan Eyecare". (set up in my Dev Dashboard Sandbox) My curl is simply following the example. What am I doing wrong? Kind regards, David

https://sandbox-api.veem.com/auth

I followed the README steps on https://github.com/veeminc/veem-java-sdk Running "./gradlew build" resulted 24 out of 47 failed tests. I'm copying one of the

I'm trying to connect to your API using Ruby's OAuth2 gem (https://github.com/oauth-xx/oauth2). I've created an account in the sandbox here, and followed the process as well as I can understand from the documentation. It appears that I'm receiving a token, but when I make a request with it, I get back the subject line. More accurately: {"code":100,"message":"Unexpected error has occurred. We apologize for the inconvenience."} Here's the series of commands I'm sending: client = OAuth2::Client.new('<client_id>', '<client_secret>', site: 'https://sandbox-api.veem.com') client.auth_code.authorize_url(redirect_uri: 'http://localhost:3000/oauth2/callback') token = client.client_credentials.get_token(redirect_uri: 'http://localhost:3000/oauth2/callback', headers: {'Authorization' => 'Basic <Base64-encoded client_id:client_secret>'}) response = token.post('/veem/v1.1/payments', params: {'notes' => 'Delivery bill', 'payee' => {'type': 'Business', 'firstName': 'Joe', 'lastName': 'Doe', 'businessName': 'BAC Inc.', 'countryCode': 'US', 'email': '[email protected]', 'phone': '19052333333'}, 'payeeAmount': {'currency': 'USD', 'number': '1000'}, 'purposeOfPayment': 'Goods'}, headers: {'X-Request-Id': '3b6a6436-561d-4643-9f83-ce837999213a'}) Any assistance you can provide would be much appreciated! Thanks, Aaron

Hello, I'm trying to get the Veem sdk, posted on Github, to work. I've installed it using Composer but I can't get the script to find the classes. I've included the autoload file. Any help would be appreciated. Thanks. Chris

Your documentation is a mess. "Get Access Token" response includes only the "access_token" field and no other tokens are present there. If I pass that "access token" into the "refresh_token" param, I get the "Invalid refresh token: <my-token-here>" error. Or is it just not possible to refresh the access token until it expires? Or refresh token will appear in the "Get Access Token" response later? I have found a similar question here https://developer.veem.com/discuss/5f87cbf4ede0f10011d29700 it was asked 6 months ago and there is still no answer posted.

Today I sent a 'createPayment' request and here's what I received in the response: { 'timeCreated': '2021-30-03T02:38:04.414Z' } ISO-8601 format is: Year-month-date API's format is: Year-date-month So those dates are not parsable using ISO-8601, at least on the sandbox env. Does the LIVE environment have the same issue?

We're working on a Veem integration for a client's invoice software. We were trying to sign up for a developer account and we're getting an error when we try to create the account. The error message says "Something went wrong. We are terribly sorry." The console says we received a 500 error from the `https://sandbox-api.veem.com/api/customers/developers` endpoint.

Can you please help reset password?

How do we get a Refresh Token?