PCI Payment Form provider setup
Use Auric or PCI Proxy payment fields to collect visitor details and display them to the operator during an assisted payment.
What it is
The PCI Payment Form supports Auric and PCI Proxy. Visitors enter payment information through embedded payment fields, and the operator opens a provider-backed view to use the submitted details. Tokens connect these steps within the payment workflow.
Who uses it and why
- Visitors submit card details through the payment form.
- Operators use the time-limited payment-detail view to process a charge in their payment system.
- Administrators and developers coordinate the merchant account and integration with Powerfront.
Where to find it
Powerfront manages the provider configuration under Settings › General Settings › PCI Payment Form. Ask Powerfront to set up or change the provider on your behalf.
Operators and visitors encounter the provider fields inside the payment workflow. There is no separate client token-management screen.
How it works
- The payment workflow opens the selected provider's entry form for the visitor.
- The visitor supplies the required billing and card information. Invalid or missing values keep the form from progressing.
- The provider returns references to the submitted details so the workflow can progress to operator processing.
- The operator opens the payment-detail view and uses the details in their POS. The card-display timer runs for four minutes from the start of retrieval, rather than restarting whenever the panel is reopened.
- Completing, cancelling or timing out closes the workflow. For Auric, INSIDE requests deletion of the billing, card and CVV tokens after closure.
Configure it
Ask Powerfront to select Provider and configure your merchant account. Auric uses Configuration, MTID, Segment, Secret, Retention and Production Account. PCI Proxy uses Merchant ID and its own Secret.
Agree the appropriate provider retention with Powerfront. Retention concerns provider sessions and tokens; it does not set how long INSIDE keeps the payment-request record or conversation.
Developers should test both visitor entry and operator display as part of the assisted-payment integration, including cancellation and timeout.
Settings
| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Provider | Settings › General Settings › PCI Payment Form | website | Auric | Powerfront | Selects Auric or PCI Proxy for payment entry and operator display. |
| Configuration | Settings › General Settings › PCI Payment Form | website | Not set | Powerfront | Identifies the Auric configuration used for payment sessions. When not set, the payment workflow cannot be enabled. |
| MTID | Settings › General Settings › PCI Payment Form | website | Not set | Powerfront | Supplies the merchant identifier required by Auric. When not set, the payment workflow cannot be enabled. |
| Segment | Settings › General Settings › PCI Payment Form | website | Not set | Powerfront | Supplies the Auric segment for payment sessions. When not set, INSIDE supplies no segment value. |
| Secret | Settings › General Settings › PCI Payment Form | website | Not set | Powerfront | Authenticates requests to the selected provider. Each provider has its own credential; when not set, INSIDE has no credential for that provider. |
| Retention | Settings › General Settings › PCI Payment Form | website | Not set | Powerfront | Supplies the retention value sent to Auric for its payment sessions. When not set, INSIDE supplies no retention value; the provider's effective retention must be confirmed separately. |
| Production Account | Settings › General Settings › PCI Payment Form | website | Off | Powerfront | Marks the Auric account as a production account in the saved configuration. |
| Merchant ID | Settings › General Settings › PCI Payment Form | website | Not set | Powerfront | Identifies the PCI Proxy merchant account. When not set, no PCI Proxy merchant account is configured. |
Fields
| Field | Where | Required | What it is for |
|---|---|---|---|
| Name on Card | Payment Form | Yes | Supplies the cardholder name in the provider's payment form. |
| Card Number | Payment Form | Yes | Supplies the card number through the provider's payment fields. |
| Card Expiry | Payment Form | Yes | Supplies the expiry date in the payment form. |
| CVV | Payment Form | Yes | Supplies the card security code in the payment form. |
Permissions
| Permission | Lets you |
|---|---|
| PCI Payment Form | Use the enabled payment workflow and its operator payment-detail view. |
Limits and good to know
- Operators can see payment details during the permitted display period. Tokenisation does not mean that details are permanently hidden from the operator.
- Auric cleanup is a deletion request after closure, not proof that the provider has completed deletion at that instant.
- Provider behaviour differs. Do not assume Auric's token cleanup or retention controls apply to PCI Proxy.
- Chat card-number masking is separate from the payment form. Use the payment form to request card details.
- The payment form collects details for operator processing. It does not itself confirm a charge or settlement.
Depends on and works with
View all connections as a list
This feature uses
- PCI Payment Form in web chatRelated
The assisted payment workflow uses the configured provider for visitor entry and operator display.
- Credit card maskingRelated
Payment-form enablement also activates chat card-number masking, which protects message text separately.
Used by
- PCI Payment Form in web chatRequires
Provider-hosted fields collect and display payment details.
FAQ and troubleshooting
Why have the payment details disappeared?
The display period may have expired, or the form may have closed. Check the payment result in your payment system before arranging another request.
Can the operator reopen the panel to get another four minutes?
No. The timer follows the start of payment-detail retrieval for that form.
Why won't the provider form load?
Ask Powerfront to check provider credentials and the full website payment-form setup. Selecting a provider alone is insufficient.
Does Retention delete our chat history?
No. It is a provider-session setting for Auric. Conversation and payment-record retention are separate.