1. Home
  2. /
  3. Web Enablement
  4. /
  5. Web Enablement – SOP
  6. /
  7. Payment method selection

Payment method selection

This Standard Operating Procedure (SOP) describes the process for selecting different payment method utilizing IP1 Web Services.

This is sub-process for the different ordering scenarios outlined in:

Procedure

It is your responsibility to ensure that you understand this procedure before performing the following tasks.

Note

Deviations from this procedure should be covered by procedures written by your company. Before performing any tasks please ensure all the business rules are set-up accordingly. 

Process overview

This section documents the Headline Processes for the web user to view & select preferred payment method when paying for an order, or paying outstanding invoices on their account.

It assumes:

  • Website has already created an anonymous or registered session
  • For ordering scenario, assumes that user has completed their shopping cart, commenced check out process and has finalized other order settings such as freight options which might affect the total order value.
  • For payment of account (B2B only), assumes user has already selected which invoice(s) they wish to pay. 

Depending on business rules for each implementation, clients may tailor which payment methods are available to the web user. This can be configured based on:

  • Customer debtor classification, payment terms and/or customer classification code(s)
  • Order Type

Back end IP1 is normally configured to allow payment by:

  1. On Account (for B2B orders only)
  2. Credit card
  3. Voucher

A default method may be set.

In case of Voucher payments, multiple vouchers may be used for payment and remaining balance may be paid by credit card.

Ordering scenario

  1. User is presented with payment method options from viewCart.
  2. User selects payment option for this order
  3. Website retrieves payment requirements from retrievePaymentFields and presents user with payment entry form based on values returned.
    • In case of ‘on account’, this simply gives user opportunity to review the final order amount before proceeding to finalise the order.
    • In case of credit card processing, refer Credit Card Processing
    • In case of voucher processing, refer Voucher Processing
  4. Once payment data has been collected, website executes makePayment with those details to finalise the order

Payment of account scenario

  1. User selects outstanding invoice(s) to be paid.
  2. Website executes processInvoices
  3. Website presents web user with payment method options from processInvoices
  4. User selects payment option
  5. Website retrieves payment requirements from prepareAccountPayment and presents user with payment entry form based on values returned.
  6. Once payment data has been collected, website executes payInvoices with those details to finalise the account payment
Print Friendly, PDF & Email