Payments interactive demo
Interactive demo of common platform operations.
Credit Card Tokenization
- On submit event, the sensitive data is sent directly to Jupiter's secure vault.
- A json token is returned to you in order to be saved for future references.
Credit Card Sale Operation
The Sale transaction is the most basic and most common transaction, used for the sale/purchase of goods or services. This type of transaction compares the cardholder’s credit limit to the amount specified in the transaction. If the amount specified is available, the transaction is approved by the card issuer and an approval code is returned. If the amount is not available, or the transaction is denied for any other reason by the issuer, an error message containing the reason is returned.
- The application's backend (server-side) sends an API request to the authorization endpoint (referencing the payment token, amount, etc). The authorization id is returned.
- If authorization status is successfull, we can now send the request to the Capture endpoint to complete the operation.
- The operation is persisted in the application database.
A sale operations requires two steps. First Authorization confirms that the
Buyer has provided valid payment information and reserves sufficient funding to perform the
transaction. And then Capture is initiated by the Merchant and is based on
a successful Authorization transaction.
AUTHORIZED_TRANSACTION_ID: will be generated when you execute a transaction request
- An authorization transaction is used to verify funds when the total amount of the purchase is unknown. Doing so, it allocates the amount sent for further capture and enables a certain amount you can charge or discharge from that initial authorization.
- Capture operation confirms the transaction, sending the exact amount that will be charged to the customer.
- For example, if you authorize for 10.00 USD, you can then capture from 9.95 USD up to 10.05 USD.
Refund transaction returns funds from the Merchant to the Buyer upon the Buyer’s request.
- Refund operation is done after 24 hs of the original transaction was made. For example, a customer returns an item and wants a refund.
- This operation will return a "not found" error before this time frame. If you need to refund a transaction in these conditions please refer to the VOID step documentation.
This will cancel a operation.
- A void operation is done upon 24 hs of the original transaction. A voided transaction is immediately cancelled and removed from the batch.
- A void operation can't be processed after 24 hs of the original transaction was made, for this type of operation please refer to the refund operation.
With Jupiter you can keep track of all related operations. Submitting an ID as a parameter, you can recover all the timeline related to that transaction Id. This is useful for transaction tracking and control.
- A timeline request returns all transactions associated with certain transaction Id.