Not able to create PAYFORT Sandbox test account.Where I get merchant identifier number.
How to register PAYFORT test account
How to get the merchant_identifier
How to get the access_code
How to get the service_command
I do not have any Idea about PayPort.Please share any Example program related to Swift.From PAYFORT where I create the sandbox test account
"https://www.payfort.com/get-started/".From this link, I entered the personal details once complete the details try to login to PAYFORT, not able to log in.
I've been facing similar questions and so emailed the PayFort support team. Here is the response I got:
Good afternoon and thank you for contacting PayFort.
Please be advised that in order for you to have the account created
in the SANDBOX (https://testfort.payfort.com) environment, the first
contact has to be initiated by one of our Pre-Qualifications team
members after receiving a documented request in a form of registration
from our website. (www.payfort.com)
The pre-qualification stage entails knowing the company/
organization's business and requirements. Qualifications are as
follows:
The company has a legal setup in the countries mentioned on our
website. The company's business module is supported by PayFort.
For more information about the businesses we support and countries,
please click on this link: http://www.payfort.com/payfort-faqs/
After the qualification stage, one of our Sales Representative will
get in touch with you to get a deeper view of the business so as to
suggest the payment solution that would suit your requirements.
Then only the TEST/SANDBOX account is created by our team to start the
Integration process.
If you wish to proceed, please kindly register on the above link or
send a direct email to sales-uae#payfort.com.
Register your self on https://www.payfort.com/get-started/ by giving your company info and wait for the email from PayFort. they'll send you the info about your test account.
you can login your test account on https://testfort.payfort.com and find your access code and merchant identifier from "Integeration Settings" menu and "Security Settings" option. you can also see the attached image so you can easily find the access code and merchant identifier.
the service_command is a static value "PURCHASE" in capital letters.
Related
What is the right procedure for pulling data about a customer (using OAuth to "Connect with Paypal" similar to the functionality that Stripe and Square provide) from Paypal?
The paypal documentation is confusing in two ways -
The OAuth scopes shown only have basic profile information like email, address, name, etc. and the link to the attributes page in the Account Information line item seems broken.
Other places mention that you have to sign onto the Paypal partner program to pull data on behalf of third parties.
So, for anyone that has gone through this - what is the right way to proceed/do I have to sign up to Paypal partner program? Is Permissions the right API to use?
I know broadly that connecting and fetching paypal account data is possible since, for example, Kabbage allows you to link your Paypal account and pulls data from it directly.
Connect with PayPal is so a user can click the CwPP button, sign into PayPal agreeing to give you access to certain profile information (based on the selected scopes) -- and then once they grant that permission and return, you're able to use the provided authorization code to access their profile information with its API.
In order to use CwPP in the live environment, your CwPP app has to be approved. You don't need to be in the PayPal partner program for this.
I am using express and mongodb.
I have succesfully added stripe, and i can make a test payment succesfully, i followed this tutorial: https://stripe.com/docs/checkout/express
So, my question is, what would be the steps to take, so that when a user pays, he gets a flag of "pro user" and then he can accces certain features.
what is normally the process here? are there any tuts or guidelines i can check ? thx!
Its not about stripe, you need to add the features for the paid users. Consider i have an option to show feature listing in my application which can be accessed only by paid users. If this case, you can make a flag in db for paid users when they completed there payment. Only those users can access the page others will shown a message like "Subscribe to access the page". This is the simple example to different paid and normal user functionality
i need for my application to create and generate test linked in accounts for every time i run my tests. I have researched and found only this solution which won`t work for me : https://developer.linkedin.com/legal/api-terms-of-use 2.3 Test Account
You may create up to five LinkedIn test accounts for purposes of testing your Application only. You must create the accounts manually and not via any automated means, such as scripts.
These test accounts must not interact with non-test accounts (for example, you can’t use test accounts to comment to posts on a Company Page and you can’t connect test accounts with non-test accounts, including your LinkedIn account), or override our API call limits. You must clearly identify the accounts as test accounts in the applicable account profile, and must identify these additional account profiles as “Developers” in your Application registration. You may not create any profile positions at real companies (besides your own) through the test accounts.
I will need more than 5 test accounts and also would like to skip the registration of my application into linked in with Real Data...
For facebook integration i managed to make this using https://developers.facebook.com
If someone have any suggestions or solutions please help :)
As per the terms of use you stated in your request, what you are asking for is not available via LinkedIn at the moment. You will need to change your testing strategy.
I'm working on a startup and we plan to use Plaid API or Yodlee for banking data aggregation ie credit history and previous transactions. I wanted to know about the data policy of these services from a fellow programmer who has worked on it. The sales guys give a pretty garbled view.
My questions are mainly
If one of my users had previously given their data to these
aggregators (ie maybe used Yodlee for mint) do they have to put in
each of their bank login details again if they use my service or do
they have a sort of user profile with which they can authorize my
app to view the data stored in their service.
Does Plaid API/Yodlee use the data I generate for its own uses and
do my users owe these data to these services and not me?
If I want to move out do they still hold my users data (the bank
accounts they have signed up with)as a profile on their desk?
PS: I think this question follows SO's policy but feel free to correct me if not.
I can not praise with my contribution here, because I am new user,
but would help if I can.
I have a big problem and I do not know how to solve it, please help.
In the same Paypal account with the default email address: email1#somedomain.com, there is 7 more emails:
email2#somedomain.com
email3#somedomain.com
email4#somedomain.com
email5#somedomain.com
email6#somedomain.com
email7#somedomain.com
that's the maximum allowed number of emails under one PayPal account (8).
So we are using API on several pages, and only one API signature can be done in the paypal
interface, so same API signature is used for each web page.
We would like to define where will money go - to which email address inside the same PayPal account.
We use Premium PayPal account, and we know that for logo change, email remove and so on, we would need Business account,
but for defining money receiver email address inside the same PayPal account
we suppose that it can be defined, otherwise we do not se a point of having several email addresses inside one same PayPal account.
The problem is that always is shown default email when making a purchase :S
We tried to define SUBJECT:
SUBJECT=merchantEmailAddress
N O T E: Typically, a merchant grants third-party permissions to a shopping cart...
And set merchantEmailAddress email2#somedomain.com.
In sandbox it works like a charm as soon as we put it on production, default mail is shown again.
Please if anyone had the same issue help.
Thank you very much, this forum is great and I realise that without nice people and contribution as well there would be no answers.
regards
You would not be using SUBJECT unless dealing with Permissions and making calls on behalf of 3rd party PayPal accounts.
You're working with a single PayPal account, so you won't be using SUBJECT at all. You'll use the credentials like you are already.
That said, I'm not sure I'm following you entirely what trying to send to different emails. I don't understand the end goal with that..?? The API credentials are what are going to tell the system where to drop the money, or pull data from, or whatever.
If you're just trying to get different logos to show up during checkout you can do that with parameters in your standard button code or API requests.
Let me know if that helps or not. Again, I'm not sure I'm understanding what you're after here.