This should be the name that the user is expecting to pay. For example, if you own many different businesses, make sure you use the name of the business.
An authorization grant represents the users authorization to process payment using its bank account. This is a code (string) used by the client application to obtain an access token.
The URL where a
GET request must be sent to obtain an authorization code for a user.
This is the public key that identifies your application when making requests
This is the private key used to authenticate server side requests
The URL in your app where users will be sent after authorization.
The redirect_uri must have the same domain as the application, and it must exactly match the
redirect_uri param provided during the
POST requests for user authorization.
APPLICATION URL: http://example.com GOOD REDIRECT_URI: http://example.com/oauth/callback BAD REDIRECT_URI: http://example.org
Scopes allow you to specify what type of access you wish to receive from your user. They include: payment, preapproval, authenticate, capture. The requested scopes will be displayed to the user during the authorization step.
For On-Demand payments, the scope must be specified as payment.
An unguessable random string. It is used to protect against cross-site request forgery attacks.
A highly recognisable brand for a given region/country.