/* GreenBanana Loading Overlay Styles */

/* Base styles for the loading overlay */
/* #gb-loading-overlay {
    position: fixed;
    top: 0;
    left: 0;
    width: 100%;
    height: 100%;
    display: flex;
    justify-content: center;
    align-items: center;
    z-index: 9999;
    transition: opacity 0.3s ease-out;
} */

/* Light theme specific styles */
/* html:not([data-theme='dark']) #gb-loading-overlay {
    background-color: rgba(245, 251, 235, 0.9);
} */
/* 
html[data-theme='dark'] #gb-loading-overlay {
    background-color: rgba(22, 32, 8, 0.9);
}

#gb-lottie-loader {
    width: 150px;
    height: 150px;
    display: flex;
    justify-content: center;
    align-items: center;
}

html:not([data-theme='dark']) #gb-lottie-loader svg path[fill="#6eae00"] {
    fill: #6eae00 !important;
}

html[data-theme='dark'] #gb-lottie-loader svg path[fill="#6eae00"] {
    fill: #9CD936 !important;
}

html:not([data-theme='dark']) #gb-lottie-loader svg path[fill^="rgb(57,"] {
    fill: #393a3e !important;
}

html[data-theme='dark'] #gb-lottie-loader svg path[fill^="rgb(57,"] {
    fill: #e6e6e6 !important;
}

.mintlify-loading-indicator,
.spinner,
[role="progressbar"] {
    display: none !important;
}

@keyframes pulse {
    0% {
        transform: scale(1);
    }

    50% {
        transform: scale(1.05);
    }

    100% {
        transform: scale(1);
    }
}

#gb-lottie-loader {
    animation: pulse 2s infinite ease-in-out;
} */

GreenBanana

About GreenBanana

Try Out GreenBanana

Environment

Error Codes

Rate Limits

Go-live Checklist

Overview

Creates a refund against an already processed payment. In case of some processors, you can even opt to refund only a partial amount multiple times until the original charge amount has been refunded

Refunds - Create

Updates the properties of a Refund object. This API can be used to attach a reason for the refund or metadata fields

Refunds - Update

Retrieves a Refund. This may be used to get the status of a previously initiated refund

Refunds - Retrieve

Lists all the refunds associated with the merchant, or for a specific payment if payment_id is provided

Refunds - List

Disputes - Retrieve Dispute

Disputes - List Disputes

**Use this API to initiate a payment.**

When you create a payment, it is stored with GreenBanana. At this stage, the payment intent is generated but requires confirmation from either the user or merchant to proceed.

Once confirmed (by including confirm=true and payment_method), the request is sent to the selected BNPL provider to verify if the customer is eligible for credit to proceed with the Buy Now, Pay Later (BNPL) provider.

The following request body example demonstrates how to create a payment with GreenBanana, which can be processed through any BNPL provider.

**Note:** The `metadata` field is used to carry additional information required by the BNPL provider. We have compiled all necessary metadata fields to ensure compatibility with any BNPL provider.

Payments - Create

**Use this API to confirm the payment and forward it to the BNPL provider.**

Alternatively, you can confirm the payment directly in the *Payments/Create* API by setting `confirm=true`. After confirmation, the payment may result in one of the following outcomes:

Once payments confirm is successfully completed, we will have payment status as `requires_capture` or `succeeded` indicating the amount for customer is authorized by the BNPL provider

1. **Fail** with a `failed` status.
2. **Transition** to a `requires_customer_action` status, along with a `next_action` block.
3. **Succeed**, with either:
- `succeeded` (for automatic capture), or
- `requires_capture` (for manual capture).

`BNPL providers typically use methods like `manual_capture` or `manual_multiple_capture` for capturing payments, as specified in the Payments Create request.

You can configure routing rules to process specific payments through specific connectors. If you would like to route a specific payment with specific connector you can also pass
"connector": ["connector_name"] to process the payment.


Payments - Confirm

To capture the funds for an uncaptured payment

Payments - Capture

A Payment could can be cancelled when it is in one of these statuses: `requires_payment_method`, `requires_capture`, `requires_confirmation`, `requires_customer_action`.

Payments - Cancel

To update the properties of a *PaymentIntent* object. This may include attaching a payment method, or attaching customer object or metadata fields after the Payment is created

Payments - Update

Retrieves a Payment. This API can also be used to get the status of a previously initiated payment or next action for an ongoing payment

Payments - Retrieve

Authorized amount for a payment can be incremented if it is in status: requires_capture

Payments - Incremental Authorization

Creates a session object or a session token for wallets like Apple Pay, Google Pay, etc. These tokens are used by Green Banana's SDK to initiate these wallets' SDK.

Payments - Session token

To retrieve the properties of a Payment Link. This may be used to get the status of a previously initiated payment or next action for an ongoing payment

Payment Status	Description
requires_payment_method	Once you create a payment through payments/create endpoint with no payment method attached to it, the payments object transitions to ‘requires_payment_method’.
requires_confirmation	After attaching a payment method through payments/update endpoint, the payments object requires you to confirm the payment.
requires_customer_action	Once the payment is confirmed through payments/confirm endpoint, if additional authentication is required, the payments object transitions to this state.
requires_capture	If you want to do separate authorize and capture, setting capture field to ‘manual’ during payments/create or confirm call will transition the payment object to this state after customer action succeeds.
processing	In case of automatic capture, the payments object transitions to processing state post confirm call and subsequent customer authentication if available.
succeeded	The payments object reaches success state post confirmation of successful processing from the payment processor.
failed	The payments object transitions to a failed state when the payment processor confirms the processing failure.
expired	You can expire the payments object while it is in any state except when it is under ‘processing’ or ‘succeeded’ state.

Getting Started

Key Information

Payment status life cycle