Glossary of Terms

Application Name

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.

authorization_grant

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.

Authorization URI

https://app.sign2pay.com/oauth/authorize

The URL where a GET request must be sent to obtain an authorization code for a user.

CLIENT_ID

This is the public key that identifies your application when making requests

CLIENT_SECRET

This is the private key used to authenticate server side requests

redirect_uri

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 GET and POST requests for user authorization.

APPLICATION URL: http://example.com

GOOD REDIRECT_URI: http://example.com/oauth/callback
BAD REDIRECT_URI:  http://example.org

Scope

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.

State

An unguessable random string. It is used to protect against cross-site request forgery attacks.

VIP Bank

A highly recognisable brand for a given region/country.

Glossary