Introduction
Charges can be made using different payment methods, and the desired method must be entered in the paymentSource
object of the charge. Each payment method uses a specific set of conditional parameters that are described below:
A paymentMethod
represents the billing method chosen to process the transaction, supported methods are:
PaymentMethod | Description |
---|---|
credit | Charges made from a credit card, supports as sourceType: card , token or customer |
pix | Charges made from Dynamic QRCode in PIX format, supports as sourceType: customer |
boleto | Charges made from registered Invoices (Payment slips) supports as sourceType: customer |
nupay | Charges made from Transparent Flow of Nupay for Business API, supports as sourceType: customer |
A sourceType
represents the payer’s data that will be used to process the transaction, which can be a credit card, a temporary card token, or data from a buyer:
SourceType | Description |
---|---|
card | Charges made from a tokenized card using the cardId or with open card data (cardNumber, cardHolderName, cardCvv, cardExpirationDate) |
token | Charges made from a card token for non-recurring billing using tokenId |
customer | Charges made from registered purchaser using the customerId |
Transaction Status
The possible statuses for a transaction on Malga are:
Status | Description |
---|---|
pending | Transaction created but not completed processing |
pre_authorized | Transaction successfully pre-authorized pending capture |
authorized | Transaction successfully authorized and captured |
failed | Transaction not authorized, check the error to identify the reason |
canceled | Transaction voided after being approved but not captured |
voided | Transaction voided after approved and captured |
refund_pending | Transaction awaiting chargeback that is in process |
charged_back | Transaction was challenged due to fraud, no acknowledgement of purchase or merchandise return |
Charge Traceability
The attribute appInfo
represents information related to traceability regarding billing, such as product transactions, device
transactions, and operating system transactions, assisting in the identification, mapping, and traceability of resources
generated in transactions.
caution
Passing this attribute is optional. Learn more in the Charges service.
Attribute | Description |
---|---|
Platform | Information about product transactions (checkout-sdk, vtex, magento, etc.) |
Device | Information about the device (iOS, android, windows, linux) |
System | Information about the merchant's proprietary capture system |