-
Notifications
You must be signed in to change notification settings - Fork 21
/
README.txt
134 lines (91 loc) · 5.37 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
******************************************************************************************
* Licensed by AT&T under 'Software Development Kit Tools Agreement.' 2012
* TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION: http://developer.att.com/sdk_agreement/
* Copyright 2012 AT&T Intellectual Property. All rights reserved. http://developer.att.com
* For more information contact developer.support@att.com<mailto:developer.support@att.com>
******************************************************************************************
AT&T API Platform Samples - Notary app 1
------------------------------
This application allows the user to sign a payload for sending in a New Transaction
or New Subscription request to the Payment API. The Single Pay application and the
Subscription application both use the Notary application to sign the payload in the
background before making a New Transaction or New Subscription request, and both
applications provide a link to the Notary app to view the most recent payload sent
and the received signed payload and signature.
This file describes how to set up, configure and run the VB Applications of the
AT&T API Platform sample applications. It covers all steps required to register the
application on DevConnect and, based on the generated API keys and secrets,
create and run one's own full-fledged sample applications.
1. Configuration
2. Installation
3. Parameters
4. Running the application
1. Configuration
Configuration consists of a few steps necessary to get an application registered
on DevConnect with the proper services and endpoints, depending on the type of
client-side application (autonomous/non-autonomous).
To register an application, go to https://devconnect-api.att.com/ and login with
your valid username and password. Next, choose "My Apps" from the bar at the top
of the page and click the "Setup a New Application" button.
Fill in the form, in particular all fields marked as "required".
Be careful while filling in the "OAuth Redirect URL" field. It should contain the
URL that the oAuth provider will redirect users to when he/she successfully
authenticates and authorizes your application.
NOTE: You MUST select Payment in the list of services under field 'Services' in
order to use this sample application code.
Having your application registered, you will get back an important pair of data:
an API key and Secret key. They are necessary to get your applications working
with the AT&T Platform APIs.
Initially your newly registered application is restricted to the "Sandbox"
environment only. To move it to production, you may promote it by clicking the
"Promote to production" button. Notice that you will get a different API key and secret,
so these values in your application should be adjusted accordingly.
Depending on the kind of authentication used, an application may be based on
either the Autonomous Client or the Web-Server Client OAuth flow (see
https://devconnect-api.att.com/docs/oauth20/autonomous-client-application-oauth-flow or
https://devconnect-api.att.com/docs/oauth20/web-server-client-application-oauth-flow
respectively).
2. Installation
** Requirements
To run the examples you need an IIS Server.
Download the application files from the download link published in AT&T portal
into webdomain of your IIS server.
3. Parameters
Each sample application contains a web.config file. It holds configurable parameters
described in an easy to read format. Please populate the following parameters in
web.config file as specified below:
1) api_key : This is mandatory parameter, Set the value
as per your registered appliaction 'API key'
field value.
2) secret_key : This is mandatory parameter, Set the value
as per your registered appliaction 'Secret key'
field value.
3) FQDN : This is mandatory parameter, Set it to the
end point URI of AT&T Service.
4) paymentType : subscription (This is mandatory parameter,
to specify Single Pay application or
Subscription application. Valid values are
"subscription" or "transaction".)
5) scope : PAYMENT (Scope of the ATT service that will
be invoked by the Application)
6) Amount : 1.90 (This is mandatory parameter, to specify
the transaction value and has to be in decimal
format.)
7) Category : 1 (Category of the product)
8) Channel : MOBILE_WEB
9) MerchantPaymentRedirectUrl : Set to the URL pointing to the application.
ATT platform uses this URL to return the
control back to the application after
transaction is completed. Example :
https://IIS_HOSTNAME:8080/payment/app1/Default.aspx
10) IsPurchaseOnNoActiveSubscription : false ("false" if its a new subscription)
11) SubscriptionRecurringNumber : 9999
12) SubscriptionRecurringPeriod : MONTHLY
13) SubscriptionRecurringPeriodAmount : 1 (This is optional parameter and its
default value is 1.)
Note: If your application is promoted from Sandbox environment to Production
environment and you decide to use production application settings, you must update
parameters 1-2 as per production application details.
4. Running the application
Suppose you copied the sample app files in your IIS server webroot/notary/app1/ folder.
In order to run the sample application, type in'http://IIS_HOSTNAME/notary/app1/Default.aspx'.