Payment use cases
These attributes determine the possible payment use cases.
paymentType specifies the payment use case.
Examples:
- For a single payment, set
paymentTypeto ONE_OFF andcapturetoAUTOMATIC- For an account verification request set
paymentTypetoACCOUNT_VERIFICATIONandcapturetoAUTOMATIC
The possible values for the paymentType and capture attributes are:
| Use case | paymentType | capture | Description | Mapping with SOAP attributes action/mode |
|---|---|---|---|---|
| singlePayment manual | ONE_OFF | MANUAL | The merchant: 1. receives an order for a known amount, 2. collect the payment at shipment time within 7 days. | 100/CPT 120/CPT |
| singlePayment deferred | ONE_OFF | DEFERRED | The merchant: 1. receives an order for a known amount, 2. requests Monext to collect the payment at a deferred specified date. | 100/DIFF 121/CPT |
| MonextInstallment manual | MX_INSTALLMENT | MANUAL | The merchant establishes an agreement with the buyer to pay for goods received in one or more installments over an agreed period. The merchant: 1. requests Monext to process the installments 2. collect the first payment at a later time | 100/NX |
| MonextRecurring manual | MX_RECURRING | MANUAL | These are payments for the delivery of ongoing goods or services. They have a fixed interval and fixed amount for each payment. The merchant: 1. requests Monext to process the installments 2. collect the first payment at a later time | 100/REC |
| singlePayment automatic | ONE_OFF | AUTOMATIC | The merchant: 1. receives an order for a known amount, 2. requests Monext to collect the payment right away. | 101/CPT |
| MonextInstallment automatic | MX_INSTALLMENT | AUTOMATIC | These are payments for the delivery of ongoing goods or services. They have a fixed interval and fixed amount for each payment. The merchant requests Monext: 1. to process the installments 2. collect the first payment right away. | 101/NX |
| MonextRecurring automatic | MX_RECURRING | AUTOMATIC | These are payments for the delivery of ongoing goods or services. They have a fixed interval and fixed amount for each payment. The merchant requests Monext: 1. to process the installments 2. to collect the first payment right away | 101/REC |
| accountVerification manual | ACCOUNT_VERIFICATION | MANUAL | The merchant checks validity of PAN and expiry date using an Account Verification transaction. There are many situations in wich a merchant may need to know if a card is valid, stolen, expired or frozen before initiating a transaction. | 108/CPT |
| accountVerification manual | ACCOUNT_VERIFICATION | MANUAL | TOKEN_PAN Permit to get a tokenPan. | 109/CPT |
| recurring manual | RECURRING | MANUAL | A merchant initiate a payment using stored payment details with no fixed schedule or amount and using your own processing. | |
| deprecated | 110 | |||
| deprecated | 111 | |||
| recurring manual | RECURRING | MANUAL | A merchant initiate a payment using stored payment details with no fixed schedule or amount and using your own processing. | 122/CPT |
| recurring automatic | RECURRING | AUTOMATIC | 123/CPT | |
| installment manual | INSTALLMENT | MANUAL | A merchant initiate a payment as part of a series of payments on a fixed schedule and a set amount by creating your own a payment schedule. | 124/CPT |
| installment automatic | INSTALLMENT | AUTOMATIC | 125/CPT | |
| deferredShipment manual | PRE_ORDER | MANUAL | A merchant initiates a payment on shipping with the order shipment beyond the authorisation release period. | 126/CPT |
| deferredShipment automatic | PRE_ORDER | AUTOMATIC | 127/CPT | |
| UCOF manual | UNSCHEDULED | MANUAL | An Unscheduled Card on File (UCoF) payment does not follow a fixed schedule. | 128/CPT |
| UCOF automatic | UNSCHEDULED | AUTOMATIC | 129/CPT | |
| rentalServicesPayment manual | RENTAL_SERVICES_PAYMENT | MANUAL | A merchant initiates an authorisation request for the rental of a good or service. | 130/CPT |
| rentalServicesPayment automatic | RENTAL_SERVICES_PAYMENT | AUTOMATIC | 131/CPT | |
| delayedCharge automatic | DELAYED_CHARGE | AUTOMATIC | This payment case applies to a merchant from whom a buyer has ordered and consumed a rental of goods and services that results in additional charges after the payment file has been closed. | 132/CPT |
| No show (rental service extension) automatic | NO_SHOW | AUTOMATIC | This payment case applies to a merchant from whom a buyer has booked a rental of goods and services and does not show up with a contractual commitment. | 133/CPT |
| Multiple Merchants payment manual | MULTIPLE_MERCHANTS | MANUAL | Decoupled payment across multiple merchants | 134 |
| Multiple Merchants Payment automatic | MULTIPLE_MERCHANTS | AUTOMATIC | Decoupled payment across multiple merchants | 135 |
| Bank Transfer automatic | BANK_TRANSFER | AUTOMATIC | Bank transfer | 150 |
| Capture standard | N/A | N/A | CAPTURE (Validation) | 201/CPT |
| Capture Late delevery | N/A | N/A | REAUTHORIZATION Reauthorization API REST only and advance user only, see Capture. | 202/CPT |
| Last capture (FINAL) | N/A | N/A | LAST_CAPTURE Last capture: Monext Online captures the specified amount and reverses the non captured remaining amount. | 203/CPT |
| Deprecated N/A Unauthorized card debit Now prohibited >> Authorization is now mandatory | 204/CPT | |||
| N/A | N/A | Refund | 421/CPT | |
| credit automatic | CREDIT | AUTOMATIC | This function is used to refund the buyer if the merchant has not retained the authorisation transaction ID required for the doRefund function. | 422/CPT |
| Direct debit authorization | 500/CPT |