Step 8 - Set up Stripe Customer Form

This will walk you through the process of making your page and integrating the Stripe Customer Element Form from PosiPay. This document provides an example of how to set up a payment form in the flow; you are free to configure it any way you see fit, as long as it supports the lightning web component.

Setting up Stripe Customer Form

Note: In setting up the Customer Form, you can use the previous flow that you created by ticking the Gateway Customer attribute field, or you can also create a separate flow for the Customer Form.

  1. Set up the Stripe Payment Flow.

  2. Configure the following data to the Stripe Form:

    1. Account

      1. Account id of the account record

      2. This will populate to the newly created payment instrument Account field.

    2. Gateway Account

      1. Gateway Account Id

    3. Generate Customer

      1. Set this to true to create customer

    4. Payment Method

      1. Credit Card or Direct Debit

      2. If both Payment Method

        image-20241209-232814.png

         

    5. Save Payment Source/Instrument

      1. Set to true to create payment source/payment instrument

Creating New Customer

To create new customer

  1. Gateway Customer (leave this empty)

    image-20241210-005120.png
  2. To create a new Payment Source/Payment Instrument if object exists in the org (applicable if the Save Payment Source/Instrument is set to true)

    1. Update Payment Source/Instrument (leave this empty)

Creating New Payment Source/Payment

To create a new Payment Source/Payment Instrument if an object exists in the org (applicable if the Save Payment Source/Instrument is set to true) and attach it to the existing customer

  • Populate the Gateway Customer field with the Gateway Customer ID record of the customer.

  • Update Payment Source/Instrument (leave this field empty)

Updating Existing Payment Source/Payment Instrument

To modify an existing Payment Source or Payment Instrument, please note that this process exclusively applies to Credit Cards.

  • Populate this field with Payment Source/Instrument ID

Assign or Change the Default Payment Source/ Payment Instrument of a Customer

Assign or change the default Payment Source/Payment Instrument of a customer just simply click the checkbox in the Stripe Form.

  1. Afterwards, click Next and the Stripe Customer Form will display.

If the selected payment method is a credit card, and the Is MOTO is set to TRUE, the CVC field will NOT be displayed.

Is MOTO is set to FALSE, the CVC field will display, if TRUE the CVC field will not display.

After filling in the necessary details whether the Payment Method is BECS Debit or Credit Card, click Save Payment Details and a Gateway Customer record, and, a Payment Source or Payment Instrument record will be created.

Gateway Customer

Note that if the NPC’s standard Payment Instrument object does exist in the org, the Payment Instrument will be created/updated.

If the NPC’s standard Payment Instrument object does NOT exist in the org, the Payment Source will be created/updated.

If the selected Payment Method is a Direct Debit, fill in the necessary details.

Example :

Afterwards, click Save Payment Details and will be redirected to the next window displaying the Bank Account Name.

The component will return the data from the Callout:

  Brand = visa

  Successful = TRUE (if tokenization is successful) / FALSE (if tokenization is failed)

  Response Code = The error code based on the response (if tokenization is failed)

  Response Message = The response message based on the response

  Token = The created customer

  Payment Method ID = The created payment method

  Card Bin = The first 6 digits of the provided card number

  Card Holder Name = The first 6 digits of the provided card number

  Last 4 = The last 4 digits of the provided card number

  Card Expiry = The card expiry of the card

Payment Source = The Payment Source record created from the tokenization process.

  Reference Id = Unique transaction reference identifier that will be useful for linking to-be-created record to the Gateway Transaction record.

Stripe Customer Element Form Parameters (Attributes)

 Input

To be configured when calling the lightning web component of the Stripe customer form.

PARAMETERS

DESCRIPTION

Generate Customer

Set to TRUE to display the Stripe customer form. Otherwise, the Stripe payment form will display.

Gateway Account

The gateway service provider where the tokenization process or payment process will be initiated. Make sure the provided Gateway Account record is an active gateway.

Payment Method

Determines the supported payment method of the form which is “Credit Card” for Card and “Direct Debit” for Bank Debit. For multiple payment methods, separate each payment method with a semi-colon. Make sure that the provided payment methods are supported by the Gateway Account.

Save Payment Source/Instrument

Once enabled, a Payment Source/Instrument record will be created and the token will be stored on that record. Otherwise, no Payment Source/Instrument record will be created.

Redirect URL

The URL where the page will be redirected to after a successful tokenization or payment processing.

Is MOTO

Once set to FALSE, the CVC field on the form will display. Otherwise, the CVC field will be hidden. Take note that it is advisable to enable the CVC field when the form is embedded on an external page

Email Address

The email address of the customer.

City

The city, district, suburb, town, or village of the customer’s address details.

Country

The country of the customer’s address details. Provide either the whole country name or the two-letter country code (ISO 3166-1 alpha-2).

Line 1

The address line 1 (e.g., street, PO Box, or company name) of the customer’s address details.

Line 2

The address line 2 (e.g., apartment, suite, unit, or building) of the customer’s address details.

State

The state, county, province, or region of the customer’s address details.

Postal Code

The ZIP or postal code of the customer’s address details.

Output

 The results from the process returned by the lightning web component of the Stripe customer form – no need to configure.

PARAMETERS

DESCRIPTION

Successful

Identifies if the whole tokenization process or payment process is either successful or failed. If true, it indicates that it is a success. If false, it indicates is a failure.

Brand

The card type of the Credit Card.

Card Expiry

The card expiry of the Credit Card.

Response Code

The returned result code from the parsed response.

Response Message

The returned result message from the parsed response.

Payment Source/Instrument

The Payment Source record that is created from the tokenization process.

Payment Method ID

Unique identifier of the payment method.

Token

Unique identifier of the customer where the Credit Card/Direct Debit details are linked.

Last 4

The last 4 digits of the provided card number.

Reference ID

Unique transaction reference identifier that will be useful for linking to-be-created record to the Gateway Transaction record.

Card Type

The card type of the Credit Card.

Card Expiry

The card expiry of the Credit Card.

Cardholder Name

The name on the front of the credit card.

Card BIN

The first six digits of the card number.

BSB Number

The BSB number of the bank account for Direct Debit.

Account Holder Name

The account holder name of the bank account for Direct Debit.

 

For PosiGive Configuration click this link : https://posimente.atlassian.net/wiki/spaces/~641d437d407493675d47acc3/pages/101220562