WEBVTT

1
00:00:00.200 --> 00:00:03.860
A payment step needs a clear purpose and a confirmed result.

2
00:00:04.040 --> 00:00:08.680
This lesson explains how to prepare a payment journey in Klarstig.ai.

3
00:00:08.860 --> 00:00:15.973
We will use a fifty dollar event registration as an example,
and check availability before offering a live checkout.

4
00:00:16.433 --> 00:00:21.029
Your Klarstig.ai subscription pays for your organization's plan.

5
00:00:21.209 --> 00:00:25.528
Customer payment collection lets a respondent pay your organization.

6
00:00:25.708 --> 00:00:27.684
These are separate capabilities.

7
00:00:27.864 --> 00:00:34.721
A working subscription checkout does not establish that
a public form can collect money for your event or service.

8
00:00:35.181 --> 00:00:39.682
Open Integrations and review the Stripe payment status for your workspace.

9
00:00:39.862 --> 00:00:45.013
If collection remains in final validation, keep the payment requirement in draft.

10
00:00:45.193 --> 00:00:52.188
Ask your administrator to confirm availability before
making payment a required part of a published process.

11
00:00:52.648 --> 00:00:56.227
Write down the amount, currency, and purpose of the charge.

12
00:00:56.407 --> 00:01:01.537
For our example, one event registration costs fifty United States dollars.

13
00:01:01.717 --> 00:01:04.727
Decide who handles cancellations and refunds.

14
00:01:04.907 --> 00:01:09.781
If the amount varies, define an approved calculation and check it before checkout.

15
00:01:10.241 --> 00:01:15.415
Use the supported Stripe payment interface when payment collection becomes available.

16
00:01:15.595 --> 00:01:22.452
Keep full card numbers and security codes out of
ordinary form fields, attachments, and support messages.

17
00:01:22.632 --> 00:01:28.795
Your registration form can collect the contact
details and event choices needed for the process.

18
00:01:29.255 --> 00:01:33.927
Rehearse in the configured test environment using Stripe's published test data.

19
00:01:34.107 --> 00:01:37.966
Test a successful payment, a decline, and a canceled checkout.

20
00:01:38.146 --> 00:01:40.602
Check what the respondent sees in each case.

21
00:01:40.782 --> 00:01:45.816
Test transactions help verify behavior without charging a real customer.

22
00:01:46.276 --> 00:01:50.254
Use the confirmed payment status to decide what happens next.

23
00:01:50.434 --> 00:01:55.809
A form submission or a thank-you page alone is insufficient evidence of payment.

24
00:01:55.989 --> 00:01:58.786
Keep the payment reference with the registration.

25
00:01:58.966 --> 00:02:05.045
Before repeating an uncertain attempt, inspect
the existing result to avoid duplicate charges.

26
00:02:05.505 --> 00:02:13.706
Before launch, confirm that collection is available, the amount is
correct, and the tested payment result reaches the intended workflow.

27
00:02:13.886 --> 00:02:16.576
Assign someone to handle payment questions.

28
00:02:16.756 --> 00:02:22.079
Keep the payment step out of live use until those
checks support the process you plan to offer.