Credit Card
Method: POST
Endpoint: {{env}}/api/transaction
Example
{
"ZumRailsType": "AccountsReceivable",
"TransactionMethod": "CreditCard",
"Amount": 123.45,
"Memo": "Memo",
"Comment": "This transaction is just a test from a user to wallet",
"UserId": "1d431e8b-...85452adb4eee",
"Authorize": {
"Capture": false,
"AutoExpireDays": 5
}
}Refund a Transaction
With ZÅ«m Rails, it is easy to refund Credit Card transactions. Currently we support whole/partial refunds of initial transactions. When you create a new refund, you must specify the transaction ID that you wish to refund. Creating a new refund will refund a transaction that has previously been created but not yet refunded. Funds will be refunded to the credit card that was originally charged.
Method: POST
Endpoint: {{env}}/api/transaction/{transaction_id}/refund
Chargeback
Chargeback applies only for credit card transactions and it can be accepted or disputed by the user until the due date. After the chargeback due date passes, the chargeback is accepted by default.
Accept Chargeback
Use this endpoint to accept a specific chargeback for a credit card transaction.
Method: PATCH
Endpoint: {{env}}/api/TransactionChargeback/{{TransactionChargebackId}}/accept
Dispute Chargeback
Use this endpoint to dispute a specific chargeback for a credit card transaction.
Method: PATCH
Endpoint: {{env}}/api/TransactionChargeback/{{TransactionChargebackId}}/dispute
Processing Schedule
Credit Card
Credit Card – Bambora
Transactions are sent to the processor immediately upon creation.
Authorization responses are received in real time.
Credit Card – Authorize.net
Transactions are sent to the processor immediately upon creation.
Authorization responses are received in real time.
Credit Card – Fiserv
Transactions are sent to the processor immediately upon creation.
Authorization responses are received in real time.
Settlement: transactions created before 11:00 PM ET are settled into the customer's wallet by 9:00 AM ET the next business day.
Authorization holds that are not captured/completed within 5 days are automatically canceled (released) by the processor.
Transaction Types
Using Credit Card, you can receive funds from your users. Zum Rails supports the following transaction types for Credit Card:
AccountsReceivable
Transaction Events
CreditCardInvalidRequest
When transaction has failed due to invalid request
CreditCardRejectedByIssuingBank
When transaction is rejected by issuing bank
CreditCardExpiredCard
When transaction has failed due to expired card
CreditCardSuspectedFraud
When transaction has failed due to suspected fraud
CreditCardTransactionNotPermitted
When transaction is not permitted
CreditCardContactSupport
When transaction has failed. Contact support
CreditCardInvalidMerchantSetUp
When transaction has failed due to invalid merchant setup
CreditCardSecurityViolation
When transaction has failed due to security violation
CreditCardInvalidCardOrDetails
When transaction has failed due to invalid card or card details
CreditCardLostOrStolenCard
When transaction has failed due to lost ot stolen card
CreditCardAccountClosedOrBlocked
When transaction has failed due to account closed or blocked
CreditCardDeemedHighRisk
When transaction has failed due to deemed high risk
CreditCardUnknownResponseFromIssuingBank
When transaction has failed due to unknown response from issuing bank
CreditCardCouldNotLocateOriginalTransaction
When reversal transaction has failed due to could not locate original transaction
CreditCardTransactionAlreadyReversed
When reversal transaction has failed due to already reversed
CreditCardGenericError
When transaction has failed due to generic error
CreditCardServiceUnavailable
When transaction has failed due to service unavailable
CreditCardRetryLater
When transaction has failed. Retry later
CreditCardReversalRejected
When reversal transaction is rejected
CreditCardDuplicateReversal
When reversal transaction has failed due to duplicated
CreditCardTransactionAlreadySettled
When reversal transaction has failed due to already settled
CreditCardTimeoutReversal
When reversal transaction has failed due to timeout
CreditCardDuplicateTransaction
When transaction was rejected as duplicate
CreditCardNotActivated
When transaction failed due to inactive card
Testing
Transactions
To simulate an Credit Card transaction failure, include an event name from the list above in the COMMENT field when creating a transaction. If you don't mention an event in the COMMENT, the transaction will change its status to "Completed" in the sandbox environment.
Examples:
Chargebacks
To simulate chargeback reasons and statuses, include specific keywords in the transaction's COMMENT field when creating a transaction. This will trigger a chargeback with the indicated reason and status within minutes.
For instance, if the COMMENT field has "chargebackreasonfraud chargebackstatewon" a simulated chargeback is generated with the reason "Fraud" and a pending status, which later updates to "Won."
Chargeback Reason
chargebackreasonclerical
Clerical
chargebackreasonfraud
Fraud
chargebackreasoninquiry
Inquiry
chargebackreasonquality
Quality
chargebackreasontechnical
Technical
Chargeback Status
chargebackstatepending
Pending
chargebackstateunderreview
Under Review
chargebackstatewon
Won
chargebackstatelost
Lost
Last updated
Was this helpful?