Skip to content

Commit f9542f3

Browse files
committed
Payments installation
1 parent d5d0845 commit f9542f3

File tree

3 files changed

+32
-0
lines changed

3 files changed

+32
-0
lines changed

PAYMENTS_INSTALLATION.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
# Configuring a DocuSign payments gateway
2+
3+
DocuSign offers built-in connections to multiple payment
4+
gateways. The payments example uses a demo account via the Stripe
5+
gateway service.
6+
7+
## Creating the payments gateway account
8+
9+
1. Login to demo.docusign.net and go to the Admin Tool.
10+
1. On the Integrations / Payments screen, click Stripe.
11+
1. For development, you can skip the Stripe account application
12+
by using the `Skip this account form` link:
13+
14+
![Skipping the Stripe account form](docs/stripe_skip_account_form_link.png)
15+
1. Next, your browser will show that an enabled Stripe
16+
payment gateway account has been associated with your
17+
DocuSign demo sandbox account.
18+
1. Configure the example launcher with the gateway account id shown in the Admin tool.
19+
20+
## Additional documentation
21+
See the
22+
[Managing Payment Gateways](https://support.docusign.com/en/guides/managing-payment-gateways)
23+
documentation.
24+

README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,14 @@ file:
7373
* **Signer name and email:** Remember to try the DocuSign signing ceremony using both a mobile phone and a regular
7474
email client.
7575

76+
### Payments code example
77+
To use the payments code example, first create a test payments gatway in your account.
78+
Follow the instructions in the
79+
[PAYMENTS_INSTALLATION.md](ss)
80+
file.
81+
82+
Then add the payment gateway id to the code example file.
83+
7684
## Run the examples
7785

7886
Use the bash shell to run the examples.
33.7 KB
Loading

0 commit comments

Comments
 (0)